In my dev group we use Jenkins to do the CI portion of our Maven builds for
our team but the company uses Thoughtworks GO for continuous delivery. We
are trying to improve our process such that we can tell GO to use the Maven
artifact published during the jenkins build instead of redoing the build
again.
To do this we created a generic Maven wrapper project that has a dependency
on the WAR artifact. The artifact details in the wrapper POM are
parameterized and set on the command-line.
We then use the versions-maven-plugin to update the project properties in
the POM with the latest snapshot version and then run it through the GO
pipeline.
This works pretty well for normal snapshot builds, but we'd like to trigger
the GO pipeline specifically after the Maven release build (triggered w/
Jenkins Maven Release Plugin) is published and before Jenkins picks up the
next SNAPSHOT build.
In other words there seems to be 2 builds that happen as a direct result of
the Maven release process and one that happens as a side effect of the SCM
change:
1. Current SNAPSHOT build
2. New Release build
1. How to insert GO trigger for release build before #3 happens?
3. Next SNAPSHOT build
Anyone have ideas on how to inject a command at step 2.1 to trigger GO to
deploy the release? I am drawing a blank...ack!
Thanks!
--
Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox <http://db.tt/9O6LfBX> !!
--
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.
