[
https://issues.jenkins-ci.org/browse/JENKINS-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Conlon updated JENKINS-12686:
-------------------------------------
Description:
I have a diamond build setup that runs across several machines. The first job
runs on the parent node, then kicks off jobs on multiple child nodes, as well
as on itself...then a join build is done on a grandchild node.
I have a list of predefined parameters, one of which recently failed on me
unexpectedly:
TIMESTAMP=${BUILD_ID}_${NODE_NAME}
I expect these predefined parameters to evaluate on the parent node, where they
are configured (this is how they are evaluated on the pass-off to its
children). However, I just witnessed a grandchild build (during the join
action) evaluate these environment variables from a child node (The build_id
and node_names were changed to that of a child job). I'm guessing it was
evaluated from the last job/node to finish, but that wouldn't exactly explain
all the other times this has worked correctly.
was:
I have a diamond build setup that runs across several machines. The first job
runs on the parent node, then kicks off jobs on multiple child nodes, as well
as on itself...then a join build is done on a grandchild node.
I have a list of predefined parameters, one of which recently failed on me
unexpectedly:
TIMESTAMP=${BUILD_ID}_${NODE_NAME}
I expect these predefined parameters to evaluate on the parent node, where they
are configured (this is how they are evaluated on the pass-off to its
children). However, I just witnessed a grandchild build evaluate these
environment variables during the join action, from a child node (The build_id
and node_names were changed). I'm guessing it was evaluated from the last
job/node to finish, but that wouldn't exactly explain all the other times this
has worked correctly.
> Predefined parameters on a post-join build are evaluated by a child job
> rather than parent
> ------------------------------------------------------------------------------------------
>
> Key: JENKINS-12686
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12686
> Project: Jenkins
> Issue Type: Bug
> Components: nodelabelparameter, parameterized-trigger
> Reporter: Michael Conlon
> Assignee: domi
>
> I have a diamond build setup that runs across several machines. The first job
> runs on the parent node, then kicks off jobs on multiple child nodes, as well
> as on itself...then a join build is done on a grandchild node.
> I have a list of predefined parameters, one of which recently failed on me
> unexpectedly:
> TIMESTAMP=${BUILD_ID}_${NODE_NAME}
> I expect these predefined parameters to evaluate on the parent node, where
> they are configured (this is how they are evaluated on the pass-off to its
> children). However, I just witnessed a grandchild build (during the join
> action) evaluate these environment variables from a child node (The build_id
> and node_names were changed to that of a child job). I'm guessing it was
> evaluated from the last job/node to finish, but that wouldn't exactly explain
> all the other times this has worked correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
