hi, i would use the label in config to hold branch name asnd then do a checkout including the label in the scm url via my own checkout in 1st build step if the if the variable can't be set directly in jenkins.
regards didier On Mar 7, 6:38 am, Les Mikesell <lesmikes...@gmail.com> wrote: > On Tue, Mar 6, 2012 at 11:18 PM, Didier Durand <durand.did...@gmail.com> > wrote: > > > You can insert env variables in your paths on Jenkins SCM section in > > job configuration > > > So, what you can do to avoid recreating jobs for branches is to put a > > variable for the path of the branch and set the value of the variable > > just before lanching build step ot the job. [I use this technique to > > be able to easily change at at once the URL root of the source code I > > am building in my jobs] > > > Something that I didn't try is to use a matrix job to set this > > variable successively to various values (all the possible branch > > names) and then have Jenkins run them automatically but the odds are > > good that it should work. > > How do you set something different other than the build host/label for > the matrix axis? > > -- > Les Mikesell > lesmikes...@gmail.com
