-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.476. Linux host for master and slave
Periodically having builds fail on Copy Artifacts step with following in the log
Unable to access upstream artifacts area. Does source project archive artifacts?
Build step 'Copy artifacts from another project' marked build as failure
There is no other exceptions in the Jenkins log that would indicate what the underlying failure is. The source job of the artifacts executes on the master and the job with the copy step executes on the slave.
I have not seen this problem when both jobs execute on the master.
I am also running in a shared storage configuration where the same mount of the jenkins install is available to both the master and the slaves, but I'm guessing this copy does not leverage this possibility and there is some type of request failure from the slave back to the master requesting the artifacts that must be failing.
- is related to
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-14962] Failure to copy artifacts from Master job to slave job
ikedam
added a comment - This should be fixed in copyartifact 1.26.
If you still have problems, please create a new issue and report the situation with the latest version.
ikedam
added a comment - This should be fixed in copyartifact 1.26.
If you still have problems, please create a new issue and report the situation with the latest version. 
Iura Adrian
added a comment - Issue can be reproduced when using Jenkins ver.2.102 and Copy Artifact Plugin 1.39 in the following 2 cases:
1. Have configured 2 projects (Project_A triggers Project_B ) that are also set to run concurrent builds. Each job has also set up a custom workspace as ${JENKINS_HOME}/jobs/${JOB_NAME}/workspace/${BUILD_NUMBER}
When Project_B is triggered it is supposed to copy artifacts from Project_A using "Upstream build that triggered this job" from Copy Artifact plugin. If both builds run on master they finish with success. However when they are run on a slave Project_B will fail with "Unable to access upstream artifacts area /path/to/archive/for/Project_A. Does source project archive artifacts?"
2. Same jobs as before. Project_A tries to copy an artifact from triggered Project_B (after it's finished) using "Specific build" with Build Number set to ${TRIGGERED_BUILD_NUMBER_Project_B}. Finished with success on master but when running on jenkins slaves, same error occurs.
Note: "Copy from WORKSPACE of latest completed build" works fine, but is of no help when running parallel builds.
Iura Adrian
added a comment - Issue can be reproduced when using Jenkins ver.2.102 and Copy Artifact Plugin 1.39 in the following 2 cases:
1. Have configured 2 projects (Project_A triggers Project_B ) that are also set to run concurrent builds. Each job has also set up a custom workspace as ${JENKINS_HOME}/jobs/${JOB_NAME}/workspace/${BUILD_NUMBER}
When Project_B is triggered it is supposed to copy artifacts from Project_A using "Upstream build that triggered this job" from Copy Artifact plugin. If both builds run on master they finish with success. However when they are run on a slave Project_B will fail with "Unable to access upstream artifacts area /path/to/archive/for/Project_A. Does source project archive artifacts?"
2. Same jobs as before. Project_A tries to copy an artifact from triggered Project_B (after it's finished) using "Specific build" with Build Number set to ${TRIGGERED_BUILD_NUMBER_Project_B}. Finished with success on master but when running on jenkins slaves, same error occurs.
Note: "Copy from WORKSPACE of latest completed build" works fine, but is of no help when running parallel builds.
Looks like similar error point