|
||||||||
|
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.
Patrick Hemmer I think you are confusing this resolved bug report with your desire to change the behavior of the git plugin. The git plugin relies on git's assurances that a commit SHA1 uniquely identifies the source code and its history. Since the source code and its history for a single SHA1 are the same no matter which branch we're using, the plugin does not need to build again if the SHA1 has already been built.
There have been several bug reports where users complained because duplicate builds were being generated. You're now requesting repeated builds of the same SHA1, which look like duplicate builds to the plugin.
I'm afraid you'll need to find another way to represent your desire to build the same SHA1 multiple times, with a different branch name on different builds.