|
When running a flow job that has been configured to run on an external build node (i.e. anything other than master), it doesn't really run there.
I discovered this when I added some steps to my job to copy some build artifacts into the flow job's workspace. The workspace variable was set properly for running on an external build node, but when my post-build publisher ran (specifically, the checkstyle step), it would fail because it couldn't find the files that my job had just copied into the workspace. Additionally, viewing the contents of the workspace via the UI indicated that it was empty. Lastly, I confirmed that the workspace directory on the external build node was in fact empty.
After some investigation, I discovered that the files were being copied to the correct directory – the directory that it should have been put in on the external build node – but on the master node!
If I lock down the job to run on the master node, it works fine. The build artifacts are exactly where I expect them to be, and the publisher runs successfully.
The workaround works for me in the near term, but it's not a workable long term solution. One of my Jenkins instances could have many instances of this job running in parallel, and I would have to significantly increase the number of executors on my master node to support this, which we have observed to cause instability.
|
