[JIRA] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace

[john.mel...@esentire.com (JIRA)]

Title: Message Title

John Mellor updated an issue   Jenkins / JENKINS-29688 Promotion sometimes fails to copy artifacts to workspace Change By: John Mellor Sometimes the artifact copy step is skipped for unknown reasons, resulting in a bad promotion. I can locate no useful logs to identify the issue, other than the promotion log itself showing a missed critical step. All promotions are manual, and run a shell script as the actual promotion. Log head from an incorrect promotion example log: {quote}Started by user ilijab Building remotely on buildslave4 in workspace /var/lib/jenkins/workspace/esensor-core Promoting esensor-core #93 [esensor-core] $ /bin/bash -xe /tmp/hudson5568737232874898866.sh . . .{quote} Log head from a correct promotion of the same job, run earlier  in the day with no product or build changes: {quote}Started by user wfang Building remotely on buildslave1 in workspace /var/lib/jenkins/workspace/esensor-core Promoting esensor-core #92 {color:red}Copied 2 artifacts from "esensor-core" build number 92{color} build hudson.plugins.copyartifact.CopyArtifact@144ec690 SUCCESS{quote} . . . As can be seen, the promotion sometimes copies the correct artifacts from master, and sometimes incorrectly decides not to.  Since the promotion  runs  and the related build processes will run  on an arbitrary host in the cluster, old workspace contents are generally present and it is not clear why it decides to wrongly skip the copy step. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.