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