>
> Otherwise, I think I'm left with extending the Jenkins Git Plugin with the
> option of overriding configured Branch Specifier with some environment
> variable (OVERRIDE_GIT_BRANCH_SPECIFIER) that I can pass from upstream.
>
Closely related issue btw:
https://issues.jenkins-ci.org/browse/JE
Thanks for the suggestions, Sami. I'll reply in-line:
On Friday, July 6, 2012 7:10:36 PM UTC+2, sti wrote:
>
> a) Instead of having the 3 jobs with git branch as parameter, make several
> sets of 3 jobs. Each set has a fixed branch they build from. If creating
> the jobs is too much manual work,
A pretty pickle you've gotten yourself into.
These are the options that come to mind (in no particular order):
a) Instead of having the 3 jobs with git branch as parameter, make several sets
of 3 jobs. Each set has a fixed branch they build from. If creating the jobs is
too much manual work, yo
Hi,
We have a product which is split into a number of different Git
repositories. They are built and released separately, but have dependencies
on each other that we track by using the same branch-names and tags in each
repository.
To illustrate, here are three repositories with three branches
