-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
apache-tomcat-7.0.19 - Jenkins ver. 1.409.1
Websphere Application Server 7.0.0.15 - Jenkins ver. 1.425 / 1.426
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Server VM (build 17.0-b16, mixed mode)
> uname -a
Linux wasp-01 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:52:51 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
> lsb_release -a
LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 5.5 (Tikanga)
Release: 5.5
Codename: Tikanga
apache-tomcat-7.0.19 - Jenkins ver. 1.409.1 Websphere Application Server 7.0.0.15 - Jenkins ver. 1.425 / 1.426 java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) Server VM (build 17.0-b16, mixed mode) > uname -a Linux wasp-01 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:52:51 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -a LSB Version: :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 5.5 (Tikanga) Release: 5.5 Codename: Tikanga
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.
- is related to
-
-
- Closed
-
