Details
-
Bug
-
Status: Reopened (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
Description
Our build process is split into several parameterized jobs. To make sure that these build steps are executed on a specific node, we defined a parameter with the node name the job should be executed on. Unfortunately the variable doesn't get expanded.
Proposed solution:
Values entered as labels should be expanded.
Attachments
Issue Links
- is related to
-
JENKINS-39451 Add support for dynamically selectable labels to node label plugin
-
- Open
-
Activity
Sergey Gordienko
added a comment - Hello everyone,
Plus one vote for this option from my side. I have jenkins swarm slaves in Docker ran dynamically and I need some functional to send build to exact node started for it. Using variables in node label would be really helpful in this task.
Sergey Gordienko
added a comment - Hello everyone,
Plus one vote for this option from my side. I have jenkins swarm slaves in Docker ran dynamically and I need some functional to send build to exact node started for it. Using variables in node label would be really helpful in this task. +1 from me, in my case, upstream jobs decides where to run the donwstream job, this feature will be very useful.
+1 from me too, This would be useful functionality in lots of different scenarios where we need to get the value of the label dynamically.
Mehul Oswal
added a comment - - edited +1 from me too, This would be useful functionality in lots of different scenarios where we need to get the value of the label dynamically. I would also need this functionality. It would be great to have it fixed.
We also have this requirement, using variables as content for the node label. The NodeLabel parameter plugin is not a solution as it also doesn't allow the use of variables as the default parameter value, the string entered has to match an existing node name.