|
My builds are for windows projects, but this issue would be the case with any project I assume.
I have a build that is using a label, "win", which both winbuila01 and winbuilda02 are labelled with.
Sometimes, the build happens on winbuila01:
Started by user Charles Mathis
Building remotely on winbuila01 in workspace d:\jenkins-slave\workspace\Deployer
Using remote perforce client: jenkins_deployer--667683261
[...successfully builds...]
Notifying upstream projects of job completion
Finished: SUCCESS
But the promotion happens on winbuilda02:
Started by user chmathis
Building remotely on winbuilda02 in workspace D:\jenkins-slave\workspace\Deployer
Promoting Deployer #173
[Deployer] $ cmd /c call C:\Windows\TEMP\hudson791959618011257982.bat
[...unsuccessfully promotes...]
Notifying upstream projects of job completion
Finished: FAILURE
I would expect one of two things:
1) It to run the promotion on winbuila01 since it built it on winbuilda01
or
2) Copy down the build artifacts to winbuilda02 so that it can run the promotion there
Neither seem to happen.
Am I missing something? Or is this a bug?
---------------------
The obvious workaround is to set the build to specific box instead of a label so that the build and promotions jobs do not roam, but that defeats the purpose of using slaves. ![]()
|
