|
||||||||
|
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 just ran into this bug myself, although not with bitbucket. It comes down to how the notifyCommit hook handles receiving a sha1 hash parameter. It actually triggers a build solely for the provided commit referenced in the sha1 parameter passed to notifyCommit instead of attempting to merge that commit into the integration branch. The workaround is to not send the sha1 parameter if possible. I'd like to see this fixed, but I expect it's more deeply ingrained in how the merging strategy works.