Required Data Pipeline Job Hangs
This article describes how to collect the minimum required information for troubleshooting pipeline jobs hang issues.
If the required data is bigger than 50 MB, you cannot use ZenDesk to upload all the information. In this case, we encourage you to use our upload service to attach all the required information.
Required Data checklist
-
Time around the issue is exposed
-
A support bundle created when the issue is exposed
-
The name of the pipeline job which is in this situation
-
The full build directory in the
$JENKINS_HOMEof the failed build -
On the agent side, capture the durable task directory (something like
/home/my-user/my-agent/workspace/pipeline-job@tmp)
Time around the issue is exposed
Grab the time around the issue is exposed so it is possible to correlate the build console logs with the Jenkins controller logs when the issue is exposed. Ideally, you will be using the Timestamper plugin so the build console logs appear with a timestamp per line.
Support Bundle
A support bundle from the problematic instance, ideally when the issue is happening or, in the worst case, right after the issue is exposed. Please follow the article below in case you don’t know how to generate a support bundle.
The name of the pipeline job which is in this situation
Take note of the hanging pipeline’s full name (including parent folder names). In case several pipeline jobs are hanging, we suggest you grab a couple of names.
The full build directory in the $JENKINS_HOME of the failed build
Check the build number that is failing and generate a build support bundle or access the $JENKINS_HOME to collect the full build directory of the failed build. See How to get a Build directory?