The join plugin doesn't work with the build pipeline plugin. However you can achieve pretty much the same thing by wrapping up multiple jobs a build steps using the parametrised triggers plugin
In terms of passing artefacts down a pipeline of jobs, what I tend to do is pass a unique identifier along the pipeline that is used to publish the built artefact early on and to retrieve built artefacts later on. You can use the copy artefact plugin to pass built artefacts around as well On Thu, Feb 16, 2012 at 12:44 PM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > On Wed, 15 Feb 2012, Jeff wrote: > > > I'm trying to implement Jenkins with Maven as the build CI/CD tool since > it > > does so well with the technologies we are using out of the box instead of > > GO that the larger .NET-based organization is using. > > > > I've done Jenkins jobs for stand-alone projects but not jobs chained from > > dependent projects. > > > > Conceptually, I can see how dependent jobs are configured using the build > > pipeline plugin (though we only have one project so far). What is > unclear > > is how downstream jobs are configured to consume the > > artifacts and/or outputs produced upstream. > > > Plugins to check out: > > * Join plugin > * Copy Artifacts plugin > > > Those might meet your needs, I use them both heavily to create longish > pipelines. > > - R. Tyler Croy > -------------------------------------- > Code: http://github.com/rtyler > Chatter: http://twitter.com/agentdero > rty...@jabber.org >
