Hi all, I'm having some trouble configuring the Jenkins maven plugin. tl,dr, in case I'm missing a simple solution: I want to run "mvn test" when a build is triggered by a new version of a snapshot dependency, but "mvn deploy" when a build is triggered by SCM changes. I can't figure out how to do this.
Backstory: we have a homegrown ant + ivy + jenkins build system, and I'm trying to figure out how practical it would be to migrate to Maven. General setup: - we have several dozen Java projects, with fairly complex dependency chains between them (almost all projects depend on a couple of generic libraries which are under active development) - all projects deploy as snapshot builds to an ivy repository. All projects which depend on on internal projects depend on the current snapshot version of that project. - when any project has source changes, jenkins picks up the SCM change and deploys a new snapshot version. - when an upstream project builds and deploys a new snapshot, Jenkins runs tests on all downstream projects but does NOT deploy. This is is done via dark Ant magic. I'm having a hard time replicating the last point using Jenkin's maven plugin. We can't deploy new snapshots on every build because developers would spend most of their day downloading new snapshot versions (each project builds dozens of times a day, since some upstream projects are under very active development.) Any thoughts on how to configure jenkins' maven plugin to run different goals on SCM changes vs dependency changes? Thanks in advance, Ben -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
