|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I am reasonably confident that in all those 30000 installations there are people who find this behaviour pretty much useless and strange. To be honest I am one of such persons. Most probably reporter of https://issues.jenkins-ci.org/browse/JENKINS-15407 would be the second one ("Then, when I commit to some branch and run curl, it started building but some other branch (ancient)")
Possibly it would be much more if '**' stayed the default setting (https://issues.jenkins-ci.org/browse/JENKINS-18820 - "As a new user to the GIT SCM, I was very surprised to find out that the default (empty) value for the Branches to Build parameter attempted to pull all branches in the repo and execute the build operation on them").
I am pretty sure that most of the 30000 installations do not use sophisticated configurations, probably it is just polling single master branch or polling simple repositories with a few leaf branches only, so they are not affected by this bug at all
To be honest I don't think the "users who depend on that behavior" really want jenkins to build several years old branches (especially that they might be so outdated that they are not buildable any longer). If a branch hasn't been updated for, let's say, a few months, then most probably there should be no point in building it. If you still think that there are people who really want to build ancient branches, could you please fix provide some configuration option for them, while fixing the bug?
BTW. What is really annoying that jenkins starts building in order from the most outdated branches to the most recent ones, ant what is really surprising - it builds branches, that would be skip during normal operations (see my other `not-a-bug': https://issues.jenkins-ci.org/browse/JENKINS-22591).
BTW2. The other annoying thing is that each build log is spoilt with hundreds of 'Seen branch in repository' lines...
Regards,
Robert