On Saturday, April 11, 2015, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> Le samedi 11 avril 2015 12:31:03 Stephen Connolly a écrit : > > I think a `finalizeGoals`, defaulting to `initialize` would suffice to > give > perhaps an "autoFinalize" boolean too, by default true, for people > requiring > the simple current 2-phase release process > > > people enough of a hook. You could then either implement a custom > lifecycle > > or attach the blue-green toggle actions to a special profile > "blue green toggle actions": what is it? In CD you often use blue-green deployment patterns. The app/site is pushed to one live environment, then when you are ready, you toggle a switch (typically either a DNS entry with a short TTL or a load balancer routing rule) and the new version is live... Then you can tear down the old version servers at your convenience (though typically they are retained as the next staging site because you'll be releasing often) thus each environment gets toggled back and forth between blue and green. > > and the push > > changes would be part of the default impl of the mojo. > > > > That would give enough of a hook while retaining simplicity. > > > > NB blue-green for most people would be promoting the staging repo. For us > > it would also include pushing the site live > oh yeah, I didn't think about it: yes, automating site release would be > great, > since it's a pain at the moment! > > big +1 > > Regards, > > Hervé > > > > > On Saturday, April 11, 2015, Robert Scholte <rfscho...@apache.org > <javascript:;>> wrote: > > > I've been thinking of a "finalize" as well, as something which could be > > > executed if a vote/stage has passed. > > > But those actions differ between organizations, which would mean either > > > introduce a lot of hooks or give an API so users can write their own > > > finalize phases > > > > > > Op Sat, 11 Apr 2015 09:38:10 +0200 schreef Stephen Connolly < > > > > > > stephen.alan.conno...@gmail.com <javascript:;>>: > > > I could see value in a release:finalize goal that is a no-op for > non-DCVS > > > > > >> but does a push changes for DCVS > > >> > > >> It would mean that you could go > > >> > > >> mvn release:prepare release:perform release:finalize > > >> > > >> in one command to close it all out > > >> > > >> On 10 April 2015 at 22:36, Robert Scholte <rfscho...@apache.org > <javascript:;>> wrote: > > >> Hmmm, no so sure about that. > > >> > > >>> The whole concept is that 'prepare' should do all the scm actions. > > >>> 'perform' should only do a checkout from the tag and run 'mvn > deploy'. > > >>> There should be as less as possible actions after uploading the > > >>> artifacts > > >>> to a repository manager. > > >>> Did you ever face issues with deploying the site (well, I did... it's > > >>> not > > >>> nice but I know the workarounds) > > >>> > > >>> the maven-release-plugin is already quite complex, we should try to > keep > > >>> the chances of a failing release as low as possible. > > >>> > > >>> Robert > > >>> > > >>> > > >>> Op Fri, 10 Apr 2015 22:49:44 +0200 schreef Mirko Friedenhagen < > > >>> > > >>> mfriedenha...@apache.org <javascript:;>>: > > >>> Hello, > > >>> > > >>>> we now have pushChanges and localCheckout in the release:prepare > goal. > > >>>> IMO pushing commits and tags after a successful release:perform or > > >>>> release:stage would be a good thing then, as this will probably > > >>>> succeed most of the times. > > >>>> > > >>>> What do you think about something like pushChangesAfterPerform? > > >>>> > > >>>> > --------------------------------------------------------------------- > > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > <javascript:;> > > >>>> For additional commands, e-mail: dev-h...@maven.apache.org > <javascript:;> > > >>> > > >>> --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > <javascript:;> > > >>> For additional commands, e-mail: dev-h...@maven.apache.org > <javascript:;> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > <javascript:;> > > > For additional commands, e-mail: dev-h...@maven.apache.org > <javascript:;> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > For additional commands, e-mail: dev-h...@maven.apache.org <javascript:;> > > -- Sent from my phone
