|
||||||||
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-16384) Blocking on downstream p... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... cjo9...@java.net (JIRA)
- [JIRA] (JENKINS-16384) Blocking on downstr... 1990.a...@gmail.com (JIRA)
The issue happens very rarely (so rarely that I even thought I'd solved it by rolling back to the LTS), so these logs seem impossible to catch. All I get is a failed job every once in a while, when it's already too late to collect blocking logs.
Is there a way to collect the required kind of logs automatically?