[
https://issues.jenkins-ci.org/browse/JENKINS-11337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159670#comment-159670
]
Harry McIntyre commented on JENKINS-11337:
------------------------------------------
>From what I've been reading it sounds like the git plugin merges together all
>the monitored branches each time there is a change to one of them, and builds
>that, passing in the branch name of the one that changed as an environment
>variable.
Assuming my understanding of this is correct, and this is by design... it
sounds to me like there is a different common use case than the one that the
plugin is designed for. I think the plugin needs to be extended so that it has
an optional mode under which:
"Any time a branch changes (including when it has commits pushed to it, even if
they have already been pushed to a different branch) a new build is queued, and
that build is passed the name of the branch that changed as a variable"
Is this the lack of this the same problem that people are reporting? Does this
make any sense?
> Git plugin only triggers a build for one branch
> -----------------------------------------------
>
> Key: JENKINS-11337
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11337
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Reporter: Andreas Pakulat
> Assignee: abayer
> Priority: Critical
>
> I've just downloaded Jenkins 1.434 to see wether the last comment in
> #JENKINS-7554 from Christian Weiske is true that the newest git plugin solves
> the problems with the GIT_BRANCH/GIT_COMMIT envvars and setting the build up
> to build multiple branches.
> Unfortunately it turns out that the plugin does not support building multiple
> branches anymore at all. No matter wether I leave the branch field empty or
> add multiple branches to the build configuration it always only builds
> master. Tried with a totally fresh job so all branches need to be considered
> 'updated' and polling as well as manual building.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
