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

I'm not sure this is the same issue. Original issue was about build queue (pending jobs) while vijay's issue is about builds and workspace in the job itself. I have also observed it with 1.487 and problem disappeared after reverting to 1.486. I believe it should be reported as a new issue.