|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15335) Jenkins briefly ... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)
- [JIRA] (JENKINS-15335) Jenkins bri... [email protected] (JIRA)

thanks for opening, I just asked a question about this on jenkins-users. Here are my thoughts:
I think 1483 introduced a bug with updating the build queue via Ajax.![]()
Initially I can see the waiting jobs and after about 10 seconds there
is the automatic update via ./ajaxBuildQueue which calls <t:queue
items="${it.queueItems}"/> if I googled it right.
One changelog entry for 1483 was: Fixed the lock contention problem on
Queue.getItems() but without a correponding JIRA ticket mentioned
which looks suspicious to me.