hi Jochen, Take a look at jenkins-job-builder. With templates and macros you you'd be set. We use this almost exclusively at work with 500+ jobs and it works great.
Job descriptions are yaml files that we keep in git. Version controlled jobs FTW! -jimW Sent from my iPad > On Mar 18, 2015, at 05:08, Jochen Hinrichsen <jochen.hinrich...@kambrium.net> > wrote: > > Dear group, > > we want to follow the same rules for Jenkins jobs that our software itself > must confirm to: development in test, testing in staging, and the official > version in a production environment. Copy and paste will always work, but i'm > too lazy to do that for the 200+ jobs. Maybe something more git-ish? > > From a first glance, i can see that everything credential related is > different in the underlying xml configuration files. So a plain 1:1 copy of a > job's external xml representation will not work. > > Did someone out here already solve this problem? > > Thanks in advance > > Jochen > -- > 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/732d0cd3-a3de-4ee2-8c59-3fc96d991659%40googlegroups.com. > 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/D6077E84-F7D7-40CE-9DEF-5BA58975AD5D%40jameswest.com. For more options, visit https://groups.google.com/d/optout.
