|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Proposal for a partial workaround : https://github.com/jenkinsci/envinject-plugin/pull/17
Seems current design (to add/remove a technical buildwrapper) introduce a possible race condition :
with concurrent builds enabled, build 1 may remove buildWrapper after build 2 added one, but before it actually was used to set build 2 environment.