[chef] Re: Re: Jenkins Cookbook Refactor has landed in master!

[Tucker < >]

Absolutely.  I've stripped out some irrelevant stuff but this is the basic cookbook right now:

https://gist.github.com/tucker-altiscale/6d31f71f425e66a3ad83

It reads like there's something wrong with the Oozie script but that's beyond my scope of expertise.

On Wed, Jan 15, 2014 at 3:58 AM, Seth Chisamore < " target="_blank"> > wrote:

Tucker,

Any chance you could provide a gist with your recipe and console output from the failed Chef run?

--Seth

On Wed, Jan 15, 2014 at 4:28 AM, Tucker < " target="_blank"> > wrote:

Agreed but with caveats:

I've been refactoring a have complete wrapper recipe to work with 2.0.0.  Installing Jenkins is a no brainer.  Getting the jenkins_private_key_credentials or jenkins_ssh_slave resources to work is a different story altogether.  The end of the README mentions setting and executor private_key and a jenkins_user but that too bombs out.

This leads me to believe I'm missing something fundamental.  This is what I was trying to do when my progress came to an end:

keys['ssh'][node.jenkins.master.deployment].each do |user, key|                                                                                                                                                                              

  jenkins_private_key_credentials user do

    description user

    private_key key['privkey']

  end 

end

The keys hash is loaded from encrypted data bags and I've verified the data is what I expect.  At this point though, it's 1:30AM and I'm out of brain cells.  Pointers?

On Tue, Jan 14, 2014 at 12:46 PM, Ranjib Dey < " target="_blank"> > wrote:

\m/ . thank you, 

On Tue, Jan 14, 2014 at 11:55 AM, Seth Vargo < " target="_blank"> > wrote:

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.

---

• Changeset
• Diff - warning, this may crash your browser...

Happy cook(book)ing!

Seth Vargo

Release Engineer, Opscode

@sethvargo

--

--tucker

--

--tucker