• Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • copyartifact-plugin
    • None

      This very well could be an error in configuring and using the copyartifact plugin, but we seem to be setting it up correctly and encounter this error on two different servers, running two different application servers. We are using 1.18 of the copyartifact plugin, but have tried older versions as well and always encounter the same error.

      We have two projects Test and Test 2. Test has run a successful builds (simply creating a test.txt file in the workspace). And Test 2 uses the copyartifact plugin to copy from Test. No matter what settings we choose for the plugin, the Test 2 builds fail with the following:

      Started by user anonymous
      Unable to access workspace for artifact copy. Slave node offline?
      Build step 'Copy artifacts from another project' marked build as failure
      Finished: FAILURE

      On the WAS server, (security issues aside) it is currently running as root. The HUDSON_HOME directory is owned by root so there should be no file system permission problems. We thought this problem might be WAS related, but we can reproduce it on a tomcat server.

      Any suggestions are welcome, as we can't use this plugin at all.
      Thanks.

          [JENKINS-10758] Unable to copy artifacts

          John Wildman added a comment -

          After attaching a debugger (something we couldn't do for the initial report in our environment) we found the code:

          if (srcDir == null || !srcDir.exists())

          { console.println(Messages.CopyArtifact_MissingWorkspace()); // (see JENKINS-3330) return isOptional(); // Fail build unless copy is optional }

          Actually uses for srcDir the workspace/build/archive. This archive directory was not present in our upstream builds because we did not know we had to enable "Archive the artifacts" in the upstream job.

          Closing this and created JENKINS-10762 for the root cause.

          John Wildman added a comment - After attaching a debugger (something we couldn't do for the initial report in our environment) we found the code: if (srcDir == null || !srcDir.exists()) { console.println(Messages.CopyArtifact_MissingWorkspace()); // (see JENKINS-3330) return isOptional(); // Fail build unless copy is optional } Actually uses for srcDir the workspace/build/archive. This archive directory was not present in our upstream builds because we did not know we had to enable "Archive the artifacts" in the upstream job. Closing this and created JENKINS-10762 for the root cause.

          John Wildman added a comment -

          Resolving this issue. JENKINS-10762 has been created to describe the root cause of this.

          John Wildman added a comment - Resolving this issue. JENKINS-10762 has been created to describe the root cause of this.

          John Wildman added a comment -

          Chose the wrong priority initially. This was really a major, not a blocker.

          John Wildman added a comment - Chose the wrong priority initially. This was really a major, not a blocker.

            mindless Alan Harder
            mantis John Wildman
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: