<p>In my opinion you should treat each pipeline dependency as any other dependency.</p>

<p>Set up an artifact repo like <a href="http://www.sonatype.org/nexus/" rel="nofollow noreferrer">nexus</a> or <a href="https://www.jfrog.com/open-source/" rel="nofollow noreferrer">artifactory</a> to be used as source of artifacts.<br>
This way you can ask for latest or tagged version of an artifact inside your pipeline and push to this repo your own artifacts when the build succeed.</p>

CC BY-SA 3.0
2017-05-24T14:12:16.117Z
You could also use [ProGet](http://inedo.com/proget). There's a plugin for the integration: https://plugins.jenkins.io/inedo-proget
Karl Harnagy
CC BY-SA 3.0
2017-05-24T14:20:51.537Z
@KarlHarnagy You may wish to turn this comment in an answer (with some more details on how it solves the problem)
Tensibai
CC BY-SA 3.0
2017-05-25T02:29:43.120Z
Thanks @Tensibai having a artifact repo seems like a good way to handle that. I will look read up more about it first.
Zac Kwan
CC BY-SA 3.0
2017-05-25T02:29:59.350Z
@KarlHarnagy , If you have setup before, could you add an answer and briefly explain how it should be used?
Zac Kwan
CC BY-SA 3.0
2017-05-24T07:34:14.017Z
2017-05-24T07:34:14.017Z
Tensibai
<p>In my workplace, we are using a monolithic repo. It contains many project and micro services that run on different Jenkins pipeline. I know that using <a href="https://github.com/jenkinsci/promoted-builds-plugin" rel="noreferrer">Promoted Build Plugin</a>, we can promote build of tested artifact. </p>

<p>However as our projects depend on projects that run on a separate pipeline, I am wondering if the <a href="https://github.com/jenkinsci/promoted-builds-plugin" rel="noreferrer">Promoted Build Plugin</a> is able to promote artifact to a different pipeline. Or can the pipeline that is running head over to a separate "place" to take the last tested artifact and use it as part of its own pipeline criteria?</p>

<p>The reason we want to do this is because of integration test that depend on the existent of another build artifact. We want to be able to test on the latest build artifact that is on another pipeline. Would be even better if we can select base on the tag/version.</p>

<jenkins><jenkins-plugins><jenkins-pipeline>
Jenkins Promote Build across different pipeline?
Zac Kwan
# Jenkins Promote Build across different pipeline?

(Asked by: username_0 on 2017-05-19)

In my workplace, we are using a monolithic repo. It contains many project and micro services that run on different Jenkins pipeline. I know that using [Promoted Build Plugin](https://github.com/jenkinsci/promoted-builds-plugin), we can promote build of tested artifact.

However as our projects depend on projects that run on a separate pipeline, I am wondering if the [Promoted Build Plugin](https://github.com/jenkinsci/promoted-builds-plugin) is able to promote artifact to a different pipeline. Or can the pipeline that is running head over to a separate "place" to take the last tested artifact and use it as part of its own pipeline criteria?

The reason we want to do this is because of integration test that depend on the existent of another build artifact. We want to be able to test on the latest build artifact that is on another pipeline. Would be even better if we can select base on the tag/version.

**Tags:** jenkins, jenkins-plugins, jenkins-pipeline


---

## 1 answers

### Answer by username_1 on 2017-05-24. Score: 2 | Accepted answer

In my opinion you should treat each pipeline dependency as any other dependency.

Set up an artifact repo like [nexus](http://www.sonatype.org/nexus/) or [artifactory](https://www.jfrog.com/open-source/) to be used as source of artifacts.  
This way you can ask for latest or tagged version of an artifact inside your pipeline and push to this repo your own artifacts when the build succeed.

> **Comments:**
> **username_2**: You could also use [ProGet](http://inedo.com/proget). There's a plugin for the integration: https://plugins.jenkins.io/inedo-proget  
> **username_1**: @KarlHarnagy You may wish to turn this comment in an answer (with some more details on how it solves the problem)  
> **username_0**: Thanks @username_1 having a artifact repo seems like a good way to handle that. I will look read up more about it first.  
> **username_0**: @KarlHarnagy , If you have setup before, could you add an answer and briefly explain how it should be used?  

---

