|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I think there is some kind of misunderstanding, my bug is about git plugin behavior shortly after the job creation.
I agree that it is useful that you can push something into "master-some-description-of-the-change" branch, and the branch gets build.
But let's imagine that after 10 years of pushing changes to different branches (and assume that many of those haven't been merged to master for any reason) your jenkins server dies (e.g. because of disk failure), and you need to set up a new job on a different server.
Would you be glad if the new jenkins server build all those 10-or-less-years-old "master-something" branches? If no, how would you refine your "/master/" branch specifier to avoid building of old branches?