Hi, 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. regards didier On Mar 7, 2:10 am, Conormull <conor.mul...@gmail.com> wrote: > Hi all > > As we achieve more advanced build pipeline features with out Jenkins > jobs, we would now like to maintain those jobs in our SCM. Each time > we cut a new branch to continue developer we now find ourselves > recreating our Jenkins jobs to point to the new branch. I was just > wondering if anyone is doing something similar and who you may have > gone about it from an end to end perspective. When and how are you > uploading the newest version of the job etc. Any help would be much > appreciated. > > Kind Regards > Conor
