Issue

• The generated support bundle misses the pipeline-timings.txt
• The Jenkins logs shows exception like the following:

Apr 23, 2018 2:19:06 PM WARNING com.cloudbees.jenkins.support.SupportPlugin writeBundle
Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
java.io.IOException: <jobName> <buildNumber> did not yet start
	at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1058)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$PipelineTimings$1.writeTo(CpsFlowExecution.java:1779)
	at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:357)
	at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:271)
	at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl$1.run(SupportPlugin.java:741)
	at java.lang.Thread.run(Thread.java:748)

Environment

• CloudBees Core
• CloudBees Core on modern cloud platforms - Managed Master
• CloudBees Core on modern cloud platforms - Operations Center
• CloudBees Core on traditional platforms - Client Master
• CloudBees Core on traditional platforms - Operations Center
• CloudBees Jenkins Enterprise
• CloudBees Jenkins Enterprise - Managed Master
• CloudBees Jenkins Enterprise - Operations Center
• CloudBees Jenkins Platform - Client Master
• CloudBees Jenkins Platform - Operations Center
• CloudBees Jenkins Distribution
• Jenkins LTS
• Support Core
• Pipeline: Groovy < 2.68

Related Issues

• JENKINS-50947

Resolution

This issue happens if pipeline timings are not available for a specific build at the time that the bundle is generated. This is causes by a non graceful exception handing in the Pipeline: Groovy plugin, that has been fixed in version 2.68 of this plugin.

Solution

Upgrade the Pipeline: Groovy plugin to version 2.68 or later.