2009/4/7 Todd Thiessen <thies...@nortel.com> > > ...that is we decide when a release is ready and > > use the release plugin to do this. The CI is only producing > > snapshots on a constant basis. > > So your formal releases are produced by manually running the release > plugin? And if it fails, you manually do a rollback, depending on the > failure? > > Some of our teams wish to automate the creation of a release say every > week and include all feature and bug fixes for that week in the release. > The problem of course is that the release plugin commits changes to the > trunk. If for whatever reason the formal build fails, and no person is > there to immediately investigate and do a rollback, you could have your > trunk in an bad state which is something we of course wish to avoid. >
They could instead use the release plugin to fork trunk to a branch, and the run the release from that branch... that way if anything goes wrong trunk is still ok... Of course then you need somebody to think about merging back... but if this is over-night you can just merge automatically during the quiet period after your automatic tests have shown that the release was ok > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
