I'm sure I'm missing something conceptually, but with a modular architecture, build artifacts may still be needed in the development environments, particularly if one team is producing a module consumed by another team and they want access to the SNAPSHOT build artifacts during development.
Doesn't the "Jenkins Maven Repository" plugin effectively isolate those artifacts to the build servers, thus preventing it's use outside the Jenkins world? I'm curious also why the standard SNAPSHOT repository can't be used? Again, I'm sure I'm missing something. On Tue, Feb 21, 2012 at 3:28 AM, Nigel Magnay <nigel.mag...@gmail.com>wrote: > This is partially what the jenkins maven repository plugin [1] was built > for -- each build is exposed as a separate build repository, so you don't > need to go copying things around. > > What we do is : > > 1) Install the plugin > 2) Add the following to the jenkins settings.xml [2]: > 3) In the downstream project, add "-Pupstream" into the maven settings > 4) Check the 'Define upstream maven repository' checkbox (build > environment), and set the upstream build that you want to add as a build > repository. > > There is a bug to do with snapshot IDs in the current version - there is a > patch that is in master, but I haven't had a chance to roll a release with > it yet. I'd use 0.6.1 until it's fixed if you rely on SNAPSHOT artifacts. > > > [1] > https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Maven+Repository+Server > > [2] > <profile> > <id>upstream</id> > <repositories> > <repository> > <id>upstream</id> > <url>${env.Jenkins.Repository}</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </repository> > </repositories> > <pluginRepositories> > <pluginRepository> > <id>upstream</id> > <url>${env.Jenkins.Repository}</url> > <releases> > <enabled>true</enabled> > </releases> > <snapshots> > <enabled>true</enabled> > </snapshots> > </pluginRepository> > > </pluginRepositories> > > </profile> > > > On Thu, Feb 16, 2012 at 1:44 AM, 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 >> > > -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox <http://db.tt/9O6LfBX> !!
