[
https://issues.jenkins-ci.org/browse/JENKINS-11337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159671#comment-159671
]
Andreas Pakulat commented on JENKINS-11337:
-------------------------------------------
No I think you misunderstood our description. The Git plugin used to work like
this:
1. Look at all branches and note down which have changed
2. Kick off a new build for each branch that has changed
So if I have 5 branches and 3 changed I'd get 3 new builds in the job, one for
each branch.
> 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
