evernat commented on Improvement JENKINS-21902

About your last comment:
1) Thanks for the plugin. But a logical change, for everyone not using the monitoring plugin, would be that http://host/threadDump of Jenkins does not use Jenkins UI, in order to be independent of queue locks. Waiting for that change in Jenkins, your argument is valid anyway for the plugin.

2) A bit sad. I suppose that a Jenkins job, created just to print jstack output, does not help for the same reason. So, I have no solution to this point except the one above.

3) I am well aware that Jenkins has gone very far on too many "public in the api" locks.

Said otherwise:

  • Points 2 and 3 will not change anything to Jenkins.
  • Point 1 should motivate to create a related core issue (and a pull request) in Jenkins, speaking about the difficulty to diagnose the (queue) locks in Jenkins. And anyway, it is a valid argument for the plugin.
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/d/optout.

Reply via email to