|
||||||||
|
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.
Hm, exactly the case quoted in the issue description does not have any detached commits, it is a normal pull request branch. With this specific branch I can reliably trigger the issue by just doing `git commit --amend; git push -f origin branch-name` with no actual changes. Every new job triggered in such way fails. But I can't reproduce it on any artificially crafted branch.