Issue Type: Improvement Improvement
Assignee: Unassigned
Components: core
Created: 24/Jul/13 3:02 PM
Description:

Whilst diagnosing JENKINS-18908, I had to delve into reflecting out the contents of Jenkins.getInstance().getQueue(). That's quite hard to do unless you fire up Groovy console.

It would be very useful to be able to see, in the UI, why a build is stuck in the ResourceController, what it's waiting for, &c.

Without the digging it looked very much like an environment / ssh / bug in Jenkins, but in reality it was just an errant plugin..

Project: Jenkins
Priority: Major Major
Reporter: magnayn
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to