Ytukyg

I currently have Jenkins set up with a number of jobs, but it's proving difficult to back up because the artifacts are stored within the job directory. I'd like to back up the job configurations and artifacts separately. I'm sure I remember reading somewhere that Jenkins now has an option to store them outside the job, but I can't find this.

Is there any configuration option that does this while still making the artifacts visible from within the job on the Jenkins interface? (ie rather than merely an add-in that copies the artifacts elsewhere)

Go to your jenkins configuration page, e.g.

http://mybuildserver.acme.com/configure

At the top of the configuration page there is a "home directory" setting. Click the "advanced..." button below it.

Now set the "Workspace Root Directory" to e:jenkins-workspaces${ITEM_FULL_NAME}, and "Build Record Root Directory" to e:jenkins-builds${ITEM_FULL_NAME} or something similar.

Warning: I run Jenkins 2.7.2 and noticed that certain features don't work properly after configuring Jenkins like that. I saw problems with folders and problems with the multi-branch project plugin. Check the status of those issues if your rely on these features.

As you can see here, there are many plugins to deploy artifacts anywhere you want/need, on FTP, CIFS, Confluence, Artifactory.... especially the ArtifactsDeployer that will allow you to make a copy of the artifacts in the Jenkins Home.

Try the Use Custom Workspace build option. From the Jenkins popup help:

For each job on Jenkins, Jenkins allocates a unique "workspace
directory." This is the directory where the code is checked out and
builds happen. Normally you should let Jenkins allocate and clean up
workspace directories, but in several situations this is problematic,
and in such case, this option lets you specify the workspace location
manually.

This option is also available under advanced project properties of multi-configuration project builds.

A groovy script under "Prepare an environment for the run" will always run on the master, and this groovy script can create a symlink to where you really want artifacts archiving to archive_to which SHOULD include the job name and build number:

if (! Files.createSymbolicLink(Paths.get(currentBuild.artifactsDir.path),

                               Paths.get(archive_to.getCanonicalPath()))) {

  throw new RuntimeException("Can't create symlink to archive dir")

}

Of course (sadly) when old builds are purged by Jenkins the old artifacts are left because jenkins will not follow a symlink when purging, even if jenkins owns the symlink and the target (shame).

I workaround for that may be to point a symlink back from the new archive dir, then, when jenkins purges it's archive dir, the new symlink will dangle and a cron job can then later delete the new job archive dir

Thank you Sam, for your post, which directed me into the right direction to solve my problem.
Have been searching for a way on how can I make a symlink to the Job-Archive of a build for multibranch projects. Up to now, we used to manually search for the correct folder basename in the filesystem and added that one to the Jenkinsfile.
Now, I can simply use

jobOutputFolder = currentBuild.rawBuild.artifactsDir.path

and use that in my script.
If security is a concern, I could implement that as a shared library additionally.

Copy Artifact Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin) adds a build step for retrieving files from another project's workspace to current and work from there.