|
||||||||
|
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.
To have the job queue multiple builds, you might try the "allow concurrent builds" check box, in hopes that would not optimize away the second request to build.
I can't test the github push mechanism because I'm not willing to expose my test Jenkins server on the public internet, and I'm not willing to configure and expose a reverse proxy on the public internet.
I can only guess that the key difference is between the GitHub push notifications that you're using and the simple git hook based notifications I'm using. I removed the GitHub components from the bug report because I assumed it was generic to the git client plugin. You'll probably need to put them back, or confirm that you can see the problem without requiring a GitHub push notification.