Link artifacts to external location

[Sverre Moe]

Can Jenkins show artifacts stored in external repositories?

We want to avoid storing the build artifacts on the Jenkins server. This takes up a lot of space. Even though we have limited artifacts retention to the last 5 builds only.

archiveArtifacts allowEmptyArchive: true, artifacts: '**/*.rpm', fingerprint: true, onlyIfSuccessful: true

externalArtifact artifact: 'https://nexus.company.com/repositories/release/package-1.1.1-1.x86_64.rpm'

[Sverre Moe]

https://brokenco.de/2018/01/04/external-artifacts-jenkins.html

Not an ideal solution. More of a hack.

[Sverre Moe]

https://plugins.jenkins.io/azure-artifact-manager/

Azure Artifact Manager plugin is an Artifact Manager that allows you store your artifacts into Azure
Blob Storage.

https://plugins.jenkins.io/artifact-manager-s3/
Artifact Manager on S3 plugin is an Artifact Manager that allow you to store your artifacts into a
S3 Bucket on Amazon.

What other Artifact Managers are there for Jenkins?
Is is the plugins with the label "Artifact Uploaders"?

Publish over SSH: Does not seem to support Pipelines. Is also up for adoption

Nexus Artifact Uploader:  Seems it only supports uploading to a Maven repository.

Strange considering: "This plugin goal is to upload artifacts generated from non-maven projects to Nexus"

Perhaps I would need to make my own customer Artifact Manager.

[Dirk Heinrichs]

Am Freitag, dem 10.12.2021 um 04:58 -0800 schrieb Sverre Moe:

Publish over SSH: Does not seem to support Pipelines. Is also up for adoption

and is not an artifact manager, but a publisher (as the name says).

Nexus Artifact Uploader:  Seems it only supports uploading to a Maven repository.

Strange considering: "This plugin goal is to upload artifacts generated from non-maven projects to Nexus"

Yeah, this is pretty useless (esp. when compared to the Artifactory plugin). It

• isn't even implemented as a publisher, one has to add build steps
• can only upload one artifact at a time, so one needs to add even more build steps

so we ended up writing our own (Groovy) script to do the upload. It's still a build step, but only one...

And, btw., it's also not an artifact manager 

Bye...

Dirk

-- 

Dirk Heinrichs

Senior Systems Engineer, Delivery Pipeline

OpenText ™ Discovery | Recommind

Phone: +49 2226 15966 18

Email: dhei...@opentext.com

Website: www.recommind.de

Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach

Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.

[Sverre Moe]

From what I can tell from the Azure and S3 Artifact Manager, you can continue to use the step archiveArtifacts.

How does this step know which Artifact Manager to use?

I do not have the "Artifact Management for Builds section" in Manage Jenkins/Configure System.

Perhaps because I do not have any additional artifact managers installed.

Strange no one has made other artifact managers for like Nexus or plain file storage on a file server.

[Dirk Heinrichs]

Am Freitag, dem 10.12.2021 um 05:20 -0800 schrieb Sverre Moe:

From what I can tell from the Azure and S3 Artifact Manager, you can continue to use the step archiveArtifacts.

How does this step know which Artifact Manager to use?

Yep, the same question also came to my mind after reading the documentation for the S3 one. I can only guess that it uses S3 as soon as it's installed and configured. At least the documentation doesn't tell how to choose, and the included screen shots doesn't show a selector or similar.

[Dirk Heinrichs]

Am Freitag, dem 10.12.2021 um 13:26 +0000 schrieb 'Dirk Heinrichs' via Jenkins Users:

Am Freitag, dem 10.12.2021 um 05:20 -0800 schrieb Sverre Moe:

From what I can tell from the Azure and S3 Artifact Manager, you can continue to use the step archiveArtifacts.

How does this step know which Artifact Manager to use?

Yep, the same question also came to my mind after reading the documentation for the S3 one. I can only guess that it uses S3 as soon as it's installed and configured. At least the documentation doesn't tell how to choose, and the included screen shots doesn't show a selector or similar.

Since the plugin looks like something we might want to use this plugin in the foreseeable future, I opened a ticket to clarify that question: https://issues.jenkins.io/browse/JENKINS-67350