-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor
-
Component/s: nodelabelparameter-plugin, parameterized-trigger-plugin
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!
Â
Â