|
||||||||
|
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 think the pr builder plugin should just do the git fetch with the pull request references and then just use the symbolic name of the references (origin/pr/N/merge) instead of using any hash. But I don't know exactly how is the interaction between this plugin and the git-plugin, I'm just thinking in terms of plain git commands. I really don't see why any of the plugins should use any numeric old hash.
I'll do my best to try to reproduce this with a Java test case, but I can't promise anything because my Java-fu is practically non-existant (even when Java as a language is easy, the thousands layers of libraries are not easy to grasp at all :S).
Also, I'll take another look at JENKINS-21980 now that I have a better idea of where the issue is.