Bat calls using different workspace paths
Below is a log from a failing build. There are two bat calls back to back but the workspace path changes for some reason.
The worker node only has a single executor.
bat "tool args"
bat "tool args" - path is changed to @2
C:\jenkins\workspace\ingredient> <tool being called>
Tool output, you can see the tool reading a file in the current workspace
Parsing manifest: 'C:\jenkins\workspace\ingredient\Manifest.xml'
//second bat call - path now has an @2
[ERROR] Manifest 'C:\jenkins\workspace\ingredient@2\Build\Manifest.xml' does not exist
script returned exit code 1
Can anyone explain what is going on here?
Please sign in to leave a comment.