-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Linux
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.
- is related to
-
JENKINS-18899 Child job finishes with "SUCCESS" status even before copy-to-plugin finishes copying files from slave to master
-
- Resolved
-
[JENKINS-16818] Copying of file back to master sometimes fails but subsequent build steps still happen
Assignee | Original: Daniel Petisme [ danielpetisme ] | New: Romain Seguy [ rseguy ] |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 147646 ] | New: JNJira + In-Review [ 192514 ] |
Assigning to Romain since he seems to be the current maintainer, maybe. Any thoughts?