-
Bug
-
Resolution: Unresolved
-
Critical
-
None
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.
- is related to
-
JENKINS-39451 Add support for dynamically selectable labels to node label plugin
-
- Open
-
[JENKINS-9665] Variables used as node labes are not expanded in parameterized builds
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
I would like to give some more details. Given are the projects A, B, C, D, E and F.
1. A checks out the workspace, builds it and does an install to the local repository.
2. B gets then triggered n times, using parts of the workspace of A using the Clone Workspace SCM Plugin and generate large parts of our software. B gets executed in parallel on different nodes and copy what's generated back to the workspace of the node where A got executed on.
3. When all jobs are finished the joining job C gets triggered. C then triggers D, E and F.
4. D, E and F are executed sequentially using the workspace of A (including whats generated during the execution of B). To not set the node in each job to a specific one directly it is necessary to define the node to run on as a variable and pass it from one job to another.
Problem:
Problem is, that variables used as label for a node do not get expanded to the value given as parameter.