[chef] Jenkins Cookbook Refactor has landed in master!


Chronological Thread 
  • From: Seth Vargo < >
  • To:
  • Cc:
  • Subject: [chef] Jenkins Cookbook Refactor has landed in master!
  • Date: Tue, 14 Jan 2014 14:55:44 -0500

Ohai Chefs!

As a followup to my earlier post regarding the Jenkins refactor, I am happy to report that the complete rewrite has now landed in the master branch on GitHub!

This refactor closed a number of issues, and our team is working diligently to address or cleanup any remaining tickets before the official release to the Chef community site.

We have enabled GitHub issues on the repository (https://github.com/opscode-cookbooks/jenkins). As of today, we are no longer using JIRA to manage issues/pull requests for the Jenkins cookbook. We do still require a CLA for contributions, however.

There are a total of 93 commits, 146 files changed, and about 10,000 lines of Chef code changed in this release. As I said in the email last week, this are many breaking changes in this release, so please lock your Jenkins cookbook to the 1.x versions until you have time to upgrade:

# Berksfile
cookbook 'jenkins', '~> 1.0'
// some environment
{
  "cookbook_versions": {
       "jenkins": "~> 1.0"
  }
}

It is highly unlikely that your cookbooks will function against the new cookbook without modification!

Important Changes

  • All resources have been refactored into HWRPs
  • A fully-tested integration suite
  • Slave recipes have been removed in favor of HWRPs
  • Apache, Nginx, java, and iptables cookbooks have been removed as dependencies

There are a number of changes, all of which will be detailed in the CHANGELOG with the full release.


Happy cook(book)ing!



Seth Vargo
Release Engineer, Opscode




Archive powered by MHonArc 2.6.16.

§