[
https://issues.jenkins-ci.org/browse/JENKINS-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160970#comment-160970
]
Carsten Brandt commented on JENKINS-12545:
------------------------------------------
might be expected behavior when they are dependend:
http://jenkins.361315.n4.nabble.com/Building-multiple-branches-with-Jenkins-td3547909.html
> Jenkins should build all tracked branches that have changed when triggered by
> Github
> ------------------------------------------------------------------------------------
>
> Key: JENKINS-12545
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12545
> Project: Jenkins
> Issue Type: Bug
> Components: github
> Environment: Jenkins 1.448, Github-api plugin 1.16, Github plugin
> 1.0, Git plugin 1.1.15
> Ubuntu 9.04
> Reporter: Leon Miller-Out
> Labels: git, github, webhook
>
> I have several projects configured to build multiple branches and set to
> build when changes are pushed to Github. For example, several projects have
> origin/master and origin/development registered. It seems to build the
> correct branch when I push to a single branch on Github, but it fails to
> behave as expected in the following situations:
> 1. If I push to two branches at once, only one of them gets built. It should
> build both of them. This probably has something to do with the changelog for
> 1.1.12 at https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin that talks
> about picking branches.
> 2. If I push to one branch, then push to a second branch while the first is
> being built, the second one never gets built.
> This bug seems to force me to set up a separate job for each branch I want to
> build, which works poorly with the Github webhook (it build all of the
> branches every time). I can't switch to polling (I think) because my slave
> systems are volatile and Jenkins seems to lose track of which ref was built
> last when the slave it was built on goes away.
--
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
