I think a `finalizeGoals`, defaulting to `initialize` would suffice to give people enough of a hook. You could then either implement a custom lifecycle or attach the blue-green toggle actions to a special profile 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 On Saturday, April 11, 2015, Robert Scholte <[email protected]> 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 < > [email protected]>: > > 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 <[email protected]> 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 < >>> [email protected]>: >>> >>> >>> 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: [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] > > -- Sent from my phone
