This bug has just broken all CI infrastructure at my organization and we had to downgrade to 1.600.

Some more investigation:

  • quiet period is NOT ignored and the item actually does await in the queue until the quiet period expires
  • during the quiet period queue api (JENKINS_URL/queue/api/json) does show an item in it, but any attempt to access item's api (JENKINS_URL/queue/item/ITEM_ID/api/json), even while the item is in the quiet period results in 404
  • after the quiet period expires any attempt to access item's api also results in 404, although it should be accessible for 5 more minutes: https://issues.jenkins-ci.org/browse/JENKINS-26228?focusedCommentId=218310#comment-218310
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