-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins v2.6.1
jira-plugin v2.3
delivery-pipeline-plugin v1.0.0
OS: RHEL
The JIRA_ISSUES variable is empty in downstream jobs past the first one.
I'm trying to update the related issues as they flow through a series of chained downstream jobs. For Example: BUILD --> QA Deploy --> STAGING Deploy. I'm able to capture accumulated issues from multiple BUILD runs when running the first downstream job (QA Deploy) using the JIRA: Add related environment variables to build in the QA job and referencing the $JIRA_ISSUES variable. However, when I run the next downstream job (STAGING Deploy), $JIRA_ISSUES is empty.
How can I capture the accumulated JIRA issues in a variable in the STAGING job just like it does in the QA job?
STAGING Deploy job configuration:
jlevis Have you used this functionality before and it has worked? Have you upgraded your Jenkins version recently? I noticed that the same thing happened to me when I upgraded Jenkins version. All of a sudden parameters were no longer propagated. In our case we assured that we declared every input parameter expected in every job configuration of the pipeline (so that they could be passed downstream) and that solved the problem, thus I did not see any relation to the functionality in the delivery pipeline plugin. Could you reproduce this with a simple pipeline with an example configuration?