Archive artifacts from multi-configuration project to a shared drive

[Romain Deterre]

Hi,

I'd like to compile a code project on multiple Linux distributions and then put all the compiled artifacts on a shared drive. To do this, I have Jenkins installed on a host computer with multiple virtual machines as nodes.

I've created a multi-configuration project with only a 'Slaves' axis, on which all the virtual machines are selected. The 'Build' step works very well, and I can see the artifacts in the workspace of the individual virtual machines.

A shared drive is mounted on the host computer, and I'd like to send all the artifacts there. I think I should use the 'Copy to Slave' plugin to copy the artifacts back to the master node, and then 'ArtifactDeployer' to copy everything to the shared drive.

My issue is that the ArtifactDeployer step seems to run on the slaves, as opposed to the master.

Am I doing this the right way? If so, how can I ask for a post-build action to be run only on the master node?

Thanks

[Les Mikesell]

First, note that if you 'archive artifacts' in the job, they will
already be copied back to the master and available through the web
interface so you may not actually need to publish anywhere else. And
if you do need to also deploy to a shared drive, why can't the slave
do that as well as the master?

--
Les Mikesell
lesmi...@gmail.com

[Romain Deterre]

Thank you for the clarification about the 'archive artifacts' step.

If it's possible, I'd like to keep the shared drive mounted only on the master. The 'ArtifactDeployer' step complains that the drives are not mounted on the slaves when I run the job, that's why I wonder if there is a way to get that running only on the master. I can mount the drives on the slaves also, but is it possible then to keep the artifacts from all the slaves in separate directories? That is because all the compiled artifacts have the same name.