RE: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

Downloading the artifacts (e.g., maven-dependency-plugin) and deploying them (e.g., maven-deploy-plugin) is the easy part, the tricky part is figuring out a "unique version number" of the artifacts to pass from one pipeline step to the next so that you are picking up the "right artifacts" from

Re: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

If you have a multi-module project and the tests are run as part of the last module, you can use the deployAtEnd parameter to delay deploying of artifacts until the end of the build. chas > On Feb 14, 2018, at 7:15 PM, Eric Benzacar wrote: > > Robert, > > I think you

Re: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

Robert, I think you misunderstood my problem. It isn't a problem of defining different distributionManagement repos; like you said that is fairly easily handled using properties or -D parameters. It is more the question of what kind of plugin is required to run which says: - download all the

RE: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

Inline... -Original Message- From: Eric B [mailto:ebenza...@gmail.com] Sent: Wednesday, February 14, 2018 8:27 PM To: Maven Users List Subject: Re: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end Hi

Re: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

Hi Robert, Thanks for the suggestions. To be honest, I never thought of using regular repositories as staging repos. That being said, I do see a hiccup with the option that I'm not sure how to address. In the case where a build is rejected during the pipelline stage, how do I delete it? I

Re: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

Hi Robert, Thanks for the suggestions. To be honest, I never thought of using regular repositories as staging repos. That being said, I do see a hiccup with the option that I'm not sure how to address. In the case where a build is rejected during the pipelline stage, how do I delete it? I

RE: Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

While Nexus may not support "staging repositories", it certainly supports more than one repository so why not just create one or more repositories that serve as staging repositories. For example, Pipeline Steps: 1.) Trigger a build based on source check-in and push to stage1 repo if build

Looking for recommendations how to best use Maven in a muti-stage Pipeline build to only deploy at the end

I'm looking for recommendations for the best way to use Maven in a multi-stage Jenkins pipeline build to deploy only at the end. At the moment, I'm using Sonatype Nexus 3.x, which means i don't have the benefit of staging repos. Consequently, I have to ensure that the only released versions of