|
||||||||
|
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.
We use the Stash Jenkins Webhook v2.6.0.
That has a check box for not using SHA1 when triggering Jenkins.
That work for us and Jenkins will trigger a build that the pretested plugin handles OK.
There is a Jenkins Issue (JENKINS-24133) for the Git-plugin about handling triggers where SHA1 is used and to find the branch name.
Until that us solved I suggest using v2.6.0 of the Stash Jenkins Webhook and check for not using SHA1.