![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Gregory Boissinot
|
|
Components:
|
artifactdeployer |
|
Created:
|
02/Apr/13 7:08 AM
|
|
Description:
|
In our system we have one master and one performance slave.
- The master server run most jobs
- The slave run all time critical jobs that require a dedicated system.
Once a build is done, artifacts is copied to a storage disk on the master server once a build is done.
This is done to reduce the size of the Jenkins installation on the primary disk. The Artifactdeployer plugin does a great job, and we get the expected behaviour from all the builds that are executed on the master server.
However we get an unexpected behaviour for builds that are executed on the slave server. The artifacts are deployed relative the slave's system. So if we specify 'D:/artifacts/', then artifacts are copied to the slave's D: disk and not the D: disk on the master.
We think this is incorrect behaviour since it is now always known on what slave a build will be executed and best practice would be to always deploy artifacts from the masters perspective.
|
|
Environment:
|
Master:
Jenkins @1.506
Artifactdeployer @ 0.26
Windows 7
Slave:
Windows 7
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jon Sten
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
