Thanks both. I think that could work. There a few other problems with pipelines and Maven. I will probably open another thread for this.
Regards. On Wed, Mar 14, 2012 at 10:25 PM, Pete <peteha...@gmail.com> wrote: > We do this but do not rely on the repository manager to pull down the > artifact. We configure the Maven Jenkins build job to archive the > artifact and then in the downstream job we configure a run parameter > and execute a shell using the passed run url to download the artifact. > > On Wed, Mar 14, 2012 at 4:33 PM, Nigel Magnay <nigel.mag...@gmail.com> > wrote: > > Hard to tell without some more detail -- wouldn't the jar name be the > same > > each time anyway? > > > > You can probably craft something with a combination of copy-artifacts > > plugin, maven repository server plugin and possibly a groovy script.. > > > > > > On Wed, Mar 14, 2012 at 7:05 PM, Nicky Ramone <nixe...@gmail.com> wrote: > >> > >> Did anyone get a chance to read this? > >> > >> > >> On Tue, Mar 13, 2012 at 2:44 PM, Nicky Ramone <nixe...@gmail.com> > wrote: > >>> > >>> Hi > >>> > >>> Suppose I build a Java project with Maven and a two-stage pipeline: > >>> Stage 1: Packaging and unit-testing (here the jar is built and deployed > >>> into the repository manager) > >>> Stage 2: Deploy to QA (here the jar is grabbed from the repository > >>> manager and placed in the QA server) > >>> > >>> How can I know which artifact name and version to grab at Stage 2? > >>> > >>> Thank you. > >>> Cheers. > >>> > >> > > >
