-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.138.2, Plugin 2.35.2, Java 1.8.x, Linux
-
-
Parameterized Trigger 2.36
If Project A triggers Project B on same node, but while Project A is running the build agent it is running on disconnects abnormally (machine disconnect, network issue, etc.), what happens is that Project B is triggered on master instead of the target node.
The expected behavior is that Project B is triggered with the original node label, and ends up in the queue waiting for the target machine to reconnect, since it is no longer connected.