I'm in a similar situation as you are, but a couple of weeks behind, so just putting together a strategy for how to handle this situation. I've been looking into using the Job Generator plugin to handle this sort of thing, but haven't gotten very far with testing it yet.
----- Original Message ----- From: [email protected] To: [email protected] At: May 2 2013 09:48:06 On 02-05-2013 12:24, Pete wrote: > We have a similar setup and what we did to generate a new set of jobs > for a new branch was to create another Jenkins job that used the Jenkins > client api to create new jobs and modify the configuration of each job > to change the branch name. You can access the configuration as XML and > modify it with sed or some other tool and then post the config back to > save it. This works really well. We ended up doing more things in this > job as well that we normally manually do for a new branch like update > the maven pom versions, reset a modified since timestamp for incremental > database builds, and others. OK, thanks. Looks like someone has now made a plugin that supports this: I think I will give that a look https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin Thanks, Thomas -- 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]. For more options, visit https://groups.google.com/groups/opt_out. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
