My recommendation is to keep your release builds manual or cron based. You can add a "release:prepare -DdryRun=true -B" to your CI if you want to make sure that a future release build will work properly. The main issue with using source change detection in a CI job and running the release plugin is that you will end up in an infinite loop, and your version will be "over 9000" by morning.
My personal belief is that release builds should not be happening every hour or every few minutes. That's what snapshots are for. Whether you are agile or waterfall, the goal is to always produce a release build on code that has working features (or so developers claim anyhow). Basically, that's a piece which is best left to either human eyes, or to a set of automated testing scripts which could also kick off a release build upon success. Perhaps I take it a little too seriously -- but that's my job as an SCM engineer :) Thanks, Roy -----Original Message----- From: KARR, DAVID [mailto:[email protected]] Sent: Tuesday, September 11, 2012 11:02 AM To: Maven Users List Subject: Is the release plugin intended to be run manually? I noticed a comment in http://www.dzone.com/links/r/continuous_delivery_using_maven_3.html about not using the release plugin because it checks in POMs after updating versions, which isn't suited to a continuous delivery pipeline. Is the release plugin intended to be run manually, and not part of an automated build? The documentation for the plugin doesn't really address this question. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
