[chef] Re: Re: Re: Jenkins cookbook(s) - recommendations

[Maven User < >]

That and also how the "node name" is defaulting to FQDN - not always does dns register the name of a vm.  Setting that to ipaddress solved my last hurdle and I was able to create a new jenkins slave successfully.

Sorry about all the postings here - I'm hoping someone else can also follow my trail if they need help.  At some point, I'll submit a pull request :-/

On Fri, Oct 12, 2012 at 1:39 AM, Maven User < " target="_blank"> > wrote:

It really looks like someone did a search/replace/rename - anything that was "hudson" to "jenkins" with this cookbook - which borks MUCH of it...

I'm still finding little bits and pieces that are wrong....

On Thu, Oct 11, 2012 at 9:49 PM, Maven User < " target="_blank"> > wrote:

a few other things...

I had to log into jenkins and make sure it is listening on a particular jnlp port.

Also - there was a way to pass through credentials to the groovy script that I had to add...

Still digging...

On Thu, Oct 11, 2012 at 9:13 PM, Maven User < " target="_blank"> > wrote:

Other problem(s) were the package names were wrong.

There didn't seem to be a jenkins.slaves.* but there is a hudson.slaves.*

Still no slave added to our cluster....

Still digging....

On Thu, Oct 11, 2012 at 9:04 PM, Maven User < " target="_blank"> > wrote:

heh  -  the "#"'s in the groovy file are not making jenkins happy....

First I'll pull them all out.......