If a new pipeline is created that has the first stage set with cleanWorkingDir set to true, the job will fail on the first run (as the working directory does not yet exist). The following error is given:
[cruise] Start to prepare PipelineDEV/Label/Deploy/1/deploy_dev_app on dev-agent-01 [/var/lib/go-agent] at Mon Apr 04 16:46:22 SAST 2011
pipelines/PipelineDEV does not exist
This is for jobs that only have upstream pipelines as materials (no vcs materials, such as svn)
Not sure if this is the differenciating factor that causes the error.
Go Version: 2.1.0(11943-65dd4ee228d8)
"New job fails with cleanWorkingDir=""true"" configuration"
Comments
1 comment
Hi Brett,
Thanks for reporting this. I can confirm that this is a bug in 2.1.
it has been reported earlier and has been fixed by us in the latest 2.2 EA release.
Related posts here and here.
- Rajesh
Please sign in to leave a comment.