Skip to content

Set up a way to share artifacts between jobs

When we’ll deploy our testers on Jenkins, we’ll need a way for them to retrieve their corresponding upstream build_Tails_ISO job artifacts over NFS or HTTP.

We could probably write a code that would guess which artifacts to use for the test using the branch name and the commit ID that are part of the artifacts name. But that sound like not so much fun, and an open door to bugs.

OTOH, Jenkins is supposed to be able to store this build <-> artifacts information, as any CI server should. It sounds more relevant to use this option, for many reasons.

The ArtifactDeployer plugin seems like a good candidate but it needs testing, and probably also modifying the vagrant/provision/assets/build-tails script.

Feature Branch: puppet-tails:feature/9597-jenkins-share-artifacts-between-jobs

Parent Task: #5288 (closed)

Original created by @bertagaz on 9597 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information