I was thinking about this the other day. My plan is to create a simple 
jenkins job that manages all of my other jenkins jobs. Some of the other 
suggestions might feed into this. 

My goal is to able to bootstrap a new jenkins server in minutes for 
disaster recovery and for bringing up new development sites. 

roughly the steps would be 

   1. deploy some docker servers (we use MAAS)
   2. spin up a jenkins server instance using a Dockerfile in the devops 
   repo
   3. create this one special job and run it.  I am hoping I can define 
   this job in my Dockerfile. This job will
      1. survey MAAS for a list of jenkins build hosts and add them with 
      executors and labels based on their size
      2. pull the list of jobs from the devops repo (format TBD)
      3. create the jobs
      4. kick them off in some prescribed order (some have parameters or 
      cron properties so they need to be run once manually)
   
I would be happy to share whatever I come up with although I can't promise 
it will be very soon. Any suggestions for projects I should look at for 
integration or inspiration? 





On Wednesday, November 14, 2012 at 7:39:07 PM UTC-5, Marcin Biegan wrote:
>
> Hi, 
>
> I wanted to ask how do you handle configuring multiple jobs. We have 
> about 10 maven projects to build in at least 2 versions (trunk/ 
> branch), which makes 20 jobs, some more for additional tests, 
> releases, maybe deployment, verification, etc. Manually adding 
> permissions and adjusting configuration of jobs is cumbersome. Is 
> there a working plugin which would allow to set some 'parent' job 
> which would define default configuration? (Template Project Plugin is 
> not enough, because it 'works' only at job creation). I know also 
> about Configuration Slicing Plugin, but this will not work in my case 
> as it requires admin permissions. 
>
> Thanks 
> Marcin Biegan 
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/017b0551-1864-421c-9de7-a64e991e335e%40googlegroups.com.

Reply via email to