Frank K commented on Bug JENKINS-22157

We are seeing the exact same thing on our Jenkins environment.

The "polling" system is not reliable so we switched to push (which is also more optimal api wise) only to run in to this particular issue which again results in jobs not being built when they should have been.

Saving the configuration does "wake" it up again, something is pretty messed up here!

The refspec is however set to

+refs/pull/*:refs/remotes/origin/pr/*

not sure if that matters here since it does match (and more).

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to