Continuous Delivery challenges that belief. I am not convinced either actually. Particular for very large enterprise builds where final artifacts are in the order of gigs in size. Imagine a project that large with dozen of developers committing to the code base many times a day and releasing each and every one of those commits? Now imagine deciding which of the released builds to keep and removing the binaries you don't want to avoid confusion. That's a lot of work.
CD is a great idea. From a purely maven perspective, however, I don't think it is quite ready yet to adopt a CD model. I think some work needs to be done to bridge the differences between a SNAPSHOT build and a release build to a point where they are effectively the same and you no longer have two kinds of builds. Of course, the challenge is to retain the advantages of both and that is a challenge I don't think is as easy as it may at first sound. > -----Original Message----- > From: Lyons, Roy [mailto:[email protected]] > Sent: Tuesday, September 11, 2012 12:43 PM > To: Maven Users List > Subject: RE: Is the release plugin intended to be run manually? > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
