I encountered the same problem when I was deploying my setup. I got around this by using the “Post build task” feature and triggered a build B script to run based on parsing the build log for a certain string.
This way, build A will complete including the post build actions included in build B From: [email protected] [mailto:[email protected]] On Behalf Of krikar Sent: Tuesday, September 18, 2012 11:59 AM To: [email protected] Subject: The inner workflows of a build steps, post-build actions and nodes 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 is that Jenkins can launch a next build on Job A, before build B is done on the previous job A. * I cannot run B as a build step in A, only as a post-build action in A. * But this will cause me problems if a next instance of A is launched before B is done in the previous one, on the same node. * And this happens... Is this a bug, or is this a desired behavior of Jenkins. I'm running version 1.481 /Kristian
