<p>The answer @itai-ganot provides is the &quot;best approach&quot;.</p>
<p>A &quot;simpler&quot; alternative is to leverage Jenkins <a href="https://www.jenkins.io/doc/pipeline/steps/core/" rel="nofollow noreferrer">&quot;Archive Artifacts&quot;</a> option ; <a href="https://www.jenkins.io/doc/pipeline/tour/tests-and-artifacts/" rel="nofollow noreferrer">example here</a> and provide your QA people Read access to Jenkins instance. Intro to <a href="https://www.jenkins.io/doc/book/managing/security/#access-control" rel="nofollow noreferrer">Access Control</a></p>
<p>Be aware you should implement <a href="https://stackoverflow.com/a/63645491/598141">strategy to manage the builds and artifacts</a> or you'll quickly run out of space (or accumulate garbage).</p>
<p>You can also <a href="https://stackoverflow.com/a/64291825/598141">copy those artifacts to another job workspace or elsewhere</a>.</p>

CC BY-SA 4.0
2021-01-12T07:20:19.440Z
2021-01-12T07:26:18.100Z
2021-01-12T07:26:18.100Z
Ian W
<p>It seems to me that you're looking for an artifact store such as <a href="https://www.sonatype.com/nexus/repository-oss" rel="nofollow noreferrer">Nexus</a> or <a href="https://jfrog.com/artifactory/start-free/" rel="nofollow noreferrer">Artifactory</a>.</p>
<p>Both solutions have Jenkins plugins which will simplify the process of uploading your artifacts to them.</p>
<p>You can find an example as to how to upload artifacts from your Jenkins pipeline to Nexus in <a href="https://dzone.com/articles/jenkins-publish-maven-artifacts-to-nexus-oss-using" rel="nofollow noreferrer">this link</a> and an example for Artifactory in <a href="https://www.jfrog.com/confluence/display/JFROG/Scripted+Pipeline+Syntax" rel="nofollow noreferrer">this link</a>.</p>
<p>Both solutions are very common and relatively easy to manage and use and are known by the community for a long time so you can find many tutorials that explain how they can be used and benefit you.</p>
<p>Then, you just need to allow your QA team read access to the relevant artifacts repo and they can download whatever version of the artifacts they need.</p>

CC BY-SA 4.0
2021-01-12T00:52:13.170Z
2021-01-12T00:52:13.170Z
Itai Ganot
<p>Currently developers push to master, jenkins picks that up, builds it, and then I go to artifacts, download the APK files and upload them in a Microsoft teams group so that the QA team can download either the latest or any previous version I had uploaded before.</p>
<p>I want to change this process to make it more efficient. I want something with a UI that the QA team can go to and download whichever version of the app (APK files) they want.</p>
<p>I want it all to be automated, so as soon as I push the master, Jenkins will build and the files will eventually show in this portal, webpage or section of Jenkins and the QA team can download which ever version they want.
How can I achieve this? Is there a Jenkins plugin for this?</p>

<jenkins><continuous-integration><gitlab><jenkins-plugins>
How can I make artifacts available to the QA team with a user-friendly UI?
code511788465541441
# How can I make artifacts available to the QA team with a user-friendly UI?

(Asked by: username_0 on 2021-01-11)

Currently developers push to master, jenkins picks that up, builds it, and then I go to artifacts, download the APK files and upload them in a Microsoft teams group so that the QA team can download either the latest or any previous version I had uploaded before.

I want to change this process to make it more efficient. I want something with a UI that the QA team can go to and download whichever version of the app (APK files) they want.

I want it all to be automated, so as soon as I push the master, Jenkins will build and the files will eventually show in this portal, webpage or section of Jenkins and the QA team can download which ever version they want.
How can I achieve this? Is there a Jenkins plugin for this?

**Tags:** jenkins, continuous-integration, gitlab, jenkins-plugins


---

## 2 answers

### Answer by username_2 on 2021-01-12. Score: 4 | Accepted answer

It seems to me that you're looking for an artifact store such as [Nexus](https://www.sonatype.com/nexus/repository-oss) or [Artifactory](https://jfrog.com/artifactory/start-free/).

Both solutions have Jenkins plugins which will simplify the process of uploading your artifacts to them.

You can find an example as to how to upload artifacts from your Jenkins pipeline to Nexus in [this link](https://dzone.com/articles/jenkins-publish-maven-artifacts-to-nexus-oss-using) and an example for Artifactory in [this link](https://www.jfrog.com/confluence/display/JFROG/Scripted+Pipeline+Syntax).

Both solutions are very common and relatively easy to manage and use and are known by the community for a long time so you can find many tutorials that explain how they can be used and benefit you.

Then, you just need to allow your QA team read access to the relevant artifacts repo and they can download whatever version of the artifacts they need.


---

### Answer by username_1 on 2021-01-12. Score: 0

The answer @itai-ganot provides is the "best approach".

A "simpler" alternative is to leverage Jenkins ["Archive Artifacts"](https://www.jenkins.io/doc/pipeline/steps/core/) option ; [example here](https://www.jenkins.io/doc/pipeline/tour/tests-and-artifacts/) and provide your QA people Read access to Jenkins instance. Intro to [Access Control](https://www.jenkins.io/doc/book/managing/security/#access-control)

Be aware you should implement [strategy to manage the builds and artifacts](https://stackoverflow.com/a/63645491/598141) or you'll quickly run out of space (or accumulate garbage).

You can also [copy those artifacts to another job workspace or elsewhere](https://stackoverflow.com/a/64291825/598141).


---

