Issue
Builds may sometimes fail with the error process apparently never started in <PATH>. This seems to be most common with shell steps.
Example Log Output:
[candid] Running shell script
process apparently never started in /home/jenkins-home/workspace/Multibranch-Pipeline-master/agent_tmp/durable-b23fe10b
The aforementioned pipeline console output can correspond to Exit logs. The below log message can be found in $JENKINS_HOME/jobs/<JOB_NAME>/builds/<BUILD#>/workflow/flowNodeStore.xml:
<detailMessage>script returned exit code -2</detailMessage>
<stackTrace>
<trace>org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:341)</trace>
<trace>org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:294)</trace>
Environment
- CloudBees CI (CloudBees Core)
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
- CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
- CloudBees CI (CloudBees Core) on traditional platforms - Client controller
- CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed controller
- CloudBees Jenkins Enterprise - Operations Center
- CloudBees Jenkins Platform - Client controller
- CloudBees Jenkins Platform - Operations Center
- CloudBees Jenkins Distribution
- Jenkins LTS
- Durable Task Plugin < 1.28
Resolution
Make sure that the Durable Task Plugin is up to date for your version of Jenkins. To resolve the example errors above, an update from 1.25 to 1.28 resolved the issue.
0 Comments