Re: Efficiently copying artifacts

> scp -r jenkins-controller:/jobs/ProjectFolder/jobs/MyProject/branches/ ** /lastSuccessfulBuild/artifact/ Hi, sorry to revive an old thread but, I'm going down the `scp` route. However, upon copying `jobs/${JOB_NAME}/builds/${BUILD_ID}/archive/` to the controller node, refreshing the

Re: Efficiently copying artifacts

To whom it may concern, I ended up finding the code in Jenkins branch-api plugin that's creating that branch path segment (the NameMangler ), however

Re: Efficiently copying artifacts

I'm trying to do same, but in both directions (archiving AND copying artifacts from upstream). I wonder how the scp approach to copying artifacts would work in multibranch pipelines? Can one deterministically construct the path to a branch job's artifact folder on the controller's disk? As I

Re: Efficiently copying artifacts

I found that using that standard method is quite slow compared to scp. So I use that method to copy just a few small files, and one with GUIDs for fingerprinting, and for the big ones I do something like scp -v ${WORKSPACE}/bigfile.tar.gz

Re: Efficiently copying artifacts

Simon Richter (2015-04-25 02:02): Hi, I have a project that outputs a few large files (compiled DLL and static library) as well as a few hundred header files as artifacts for use by the next project in the dependency chain. Copying these in and out of workspaces takes quite a long time, and the

RE: Efficiently copying artifacts

Subject: Re: Efficiently copying artifacts Simon Richter (2015-04-25 02:02): Hi, I have a project that outputs a few large files (compiled DLL and static library) as well as a few hundred header files as artifacts for use by the next project in the dependency chain. Copying these in and out

RE: Efficiently copying artifacts

Are you using Archive Artifacts in the upstream job, and the Copy Artifact plugin in the downstream job? This is the standard method. If so, maybe the upstream job should produce a single zip file , which the downstream job and get and unzip. Matthew -Original Message- From: