It sounds like you want the promotion job to be reading files from the
workspace of the parent build that is being promoted.
If so, that’s the wrong way to do it. From
https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin:
Do not rely on files in the workspace
The promotion action
If the label you use to restrict the parent build the promotion build will
use the same label.
The best practice for promotion is to save artifacts during build so that
the artifacts can be retrieved during promotion. This will allow you to
perform promotions on historical builds as well and you
Yeah, that is not a scalable solution. That very effectively limits the build
and promotion to only run on one host, completely defeating the purpose of
having a cluster of slave build machines. Maybe it works ok for sites that do
not have enough peak workload to need slave machines.
It
On 26 May 2015 at 14:00, John Mellor john.mel...@esentire.com wrote:
Yeah, that is not a scalable solution. That very effectively limits the
build and promotion to only run on one host, completely defeating the
purpose of having a cluster of slave build machines. Maybe it works ok for
