|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We had the same issue, but with a job.
For example, a job was triggered at about the same time by two different parent jobs with different parameters (run A and run B). During the run B, we had environment variables corresponding to run A. After both runs, the "Environment variables" menu displays the correct parameters.
On 1.90 in Jenkins version 1.565.1