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

I agree that the problem seems to be introduced in 1.483. I have rolled back to 1.480 in the meantime.
My experience is that the queue disappears after 5 seconds or so through via ajax refresh of the queue status.