![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Daniel Petisme
|
|
Components:
|
copy-to-slave |
|
Created:
|
14/Feb/13 9:59 PM
|
|
Description:
|
My builds use this plugin to copy a parameter file from a slave back to the master Jenkins node, and then a subsequent build step sends that file to another job as a list of parameters (parameterized trigger).
There seems to be a race condition that I hit occasionally, where the downstream job is triggered with empty parameters. When I look on the master node, however, the parameter file is there/has been copied back successfully. If the same build is run again, it works. I suspect that somehow the copy is not happening/finishing before the downstream job is triggered.
|
|
Environment:
|
Linux
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
owenmehegan
|
|
|
|
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.
