Hi,
As promised, I just published the video of my conference talk about:
"Cultivating the Jenkins job jungle with Groovy"
You can find the video and all info at:
- http://youtu.be/8jQm2wqX4xc
I hope you find it interesting :)
Regards,
Patrick
On 10/29/2014 01:39 PM, Patrick van Dissel wrote:
> The JobDSL (currently) does not support having you global Jenkins config
> files managed by the DSL. So, we have the global Jenkins configs in a
> separate closed repository which we checked out manually once and is now
> kept insync with a Jenkins job :). But solutions like
> Puppet/Chef/Ansible could also help you there, we're skipping those
> solution and are currently moving to use Docker (https://www.docker.com)
> instead.
>
> For the authorization, we use a separate Jenkins job which executes a
> Groovy script. That groovy script looks at our landscape service;
> - for each application
> -- finds the team of that application
> -- adds authentication section to the jobs
> We run this job as downstream dependency of the JobDSL "Seed" job.
>
> Next week I will give a talk on the JobDSL at the dutch JFall conference
> (http://www.nljug.org/jfall/2014/) in The Netherlands. It will be mostly
> code, showing an extensive CI and CD setup with the JobDSL. And also
> showing steps how to start with the JobDSL. I will record the session
> and share the slides, video and demo code afterwards.
> I'll add the links here as soon as I have them shared :)
>
> /Patrick
>
> On 10/29/2014 12:47 PM, Maciej Jaros wrote:
>> Patrick van Dissel (2014-10-29 02:35):
>>> [...]
>>> About the jobs structure..
>>> It really depends how you're going to use Jenkins.
>>> Start simpel, and only add what is nessesary.
>>> The amount of jobs does not really matter. For your idea, with my team
>>> we currently have a Jenkins setup of 1 master with 3 slaves running a
>>> bit more then 1000 jobs. With multiple jobs for single
>>> apps/libraries/.., eg. CI, Deploy, DEV, TEST, ACC, PRO, etc. Almost all
>>> managed with JobDSL scripts.
>>
>> The JobDSL sounds very interesting! But how do you configure
>> authorization in a complex environment? I mean I'd like to put DSL in
>> SVN, but do not want to put passwords there. So two issues really:
>>
>> 1. SSH authorization (executing and sending files).
>> 2. SVN authorization.
>>
>> Regards,
>> Nux.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to [email protected]
>> <mailto:[email protected]>.
>> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/54764869.90206%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
