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


Chronological Thread 
  • From: Seth Vargo < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Jenkins Cookbook Refactor has landed in master!
  • Date: Sat, 18 Jan 2014 23:37:57 -0500

Mark,

Could you please open an issue on GitHub? It's much easier to track and share code inside GitHub issues + more people can join the conversation.

Thanks!


Seth Vargo
Release Engineer, Opscode

From: Mark Pimentel ">Mark Pimentel
Reply:  ">
Date: January 17, 2014 at 10:45:28 AM
To:  ">
Subject:  [chef] Re: Re: Re: Jenkins Cookbook Refactor has landed in master!
Having some issues with the new version and trying to register a slave node.  I have a private key for a jenkins user that I am trying to use with the jenkins_jnlp_slave resource and I keep getting a 403 from jenkins.  I tried to use the key on the cli with the jenkins cli and it is successful.

Am I missing something?



On Thu, Jan 16, 2014 at 1:28 AM, Tucker < " target="_blank"> > wrote:
Thanks for the update.  I actually assumed the credential issue was because we're using the LTS release and no the latest and greatest.  For now, I've simplified my deployment to just pushing master, prepping slaves and then hand configuring the rest.  I'm still in a better place than where I was a week ago (our Jenkins cookbooks require a lot of "massaging" every time we push them), so no complaints.  Hopefully I'll be able to find some time to dig deeper into these.

Regardless, this refactor is extremely helpful.  Thanks again.


On Wed, Jan 15, 2014 at 9:45 PM, Seth Chisamore < " target="_blank"> > wrote:
Tucker,
I was able to recreate both of your issues and opened the following tickets to track the fix work:

If you stumble across any more problems please open GitHub issues per the repo's ISSUES doc:

Thanks!

--Seth




--

--tucker



--
Thanks,

Mark




Archive powered by MHonArc 2.6.16.

§