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, 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 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.

1 Answer 1


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

Set up an artifact repo like nexus or artifactory 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.

  • You could also use ProGet. There's a plugin for the integration: plugins.jenkins.io/inedo-proget May 24, 2017 at 14:12
  • 1
    @KarlHarnagy You may wish to turn this comment in an answer (with some more details on how it solves the problem)
    – Tensibai
    May 24, 2017 at 14:20
  • 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
    May 25, 2017 at 2:29
  • 1
    @KarlHarnagy , If you have setup before, could you add an answer and briefly explain how it should be used?
    – Zac Kwan
    May 25, 2017 at 2:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.