I maybe missed a point.
This is perhaps the desired behavior when running multiple executors on one
node. But I have the corner case where I run 1 executor on 1 node. The
reason is not performance, it's the job that needs the machine all by it
self.
Also in my specific case, the job B, powers o
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of krikar
Sent: Tuesday, September 18, 2012 11:59 AM
To: jenkinsci-users@googlegroups.com
Subject: The inner workflows of a build steps, post-build actions and nodes
Hi,
I have a problem, were my node
Hi,
I have a problem, were my node/slave is 'hijacked' by another
job prematurely. But this may very well be by design. This is what happens:
- I have a job A that runs all the build steps successfully.
- In the post-build actions, I have a "Trigger parameterized build" B.
Now, my problem
