Hi,
Issue: wrong node chosen for downstream job if upstream job uses nodelabelparameter.
Sample:
Main job "A" has "This project is parameterized" with "Label=allnodes".
Also main job "A" has a Build "Trigger/call builds on other projects" which triggers job "B" passing "Current build parameters".
Job "B" has "This project is parameterized" disabled and "Restrict where this project can be run = supernode".
Result:
Job A always executed on nodes with label "allnodes" -> OK.
Job B also executes on nodes with label "allnodes" -> WRONG.
IMHO, job B should respect "This project is parameterized" and be executed on "supernode" because it has disabled "This project is parameterized".
P.S. I am not sure which plugin is guilty here, while I suspect nodelabelparameter-plugin here, as we are just trying using it now and we are using parameterized-trigger-plugin for a years without any issues.
Thank you for the reply here!
Any hints here how to make it fixed locally or at least workarounded?
Maybe some other plugin can provide proper nodelabel functionality here?
Thank you!