and other parts can be configured before actually
> running the service?
>
> On Wednesday, August 17, 2016 at 9:36:08 AM UTC-5, Jason Kulatunga wrote:
>>
>> Hey,
>> Thanks for all the help guys.
>> I slept on this idea for a few days because, to be honest I really didn't
Hey Jenkins-Users,
I was told this might interest some of you.
I'm writing a series of blog posts describing how we automate Jenkins at
scale (hundreds of Jobs, hundreds of developers, dozens of Jenkins servers
+ nodes just for our team).
Part 1 - Automated Jenkins Install using Chef
g to see how
> https://issues.jenkins-ci.org/browse/JENKINS-33507 will work for us to
> get as much of the job configuration out of Jenkins as possible.
>
> We are still in the brainstorming phase, so I'm interested to see who else
> has ran into this and what they have done.
>
&
ty config you're talking about about forbidding any upgrade would
> seem a simpler way. And probably it would your life simpler if you somehow
> have to support all those different instances which can currently be
> actually quite different.
>
> HTH
>
> Le 11 août 2016 3:1
