Hello Karl Heinz,

while I am not against moving to GitHub actions, doing a lazy 72h consensus seems a little short for me here ☺️
Best Regards
Mirko Friedenhagen

Sent from my mobile

Am 02.06.20 um 18:43 schrieb Karl Heinz Marbaise

Von: "Karl Heinz Marbaise" <[email protected]>
Datum: 2. Juni 2020
An: mojohaus-dev <[email protected]>
Cc:
Betreff: [VOTE] Migration from travis to GitHub Actions

Hi,


currently I'm working the subject to replace the travis build with GitHub actions:


https://github.com/mojohaus/mojo-parent/issues/114


Replace the CI tooling with GitHub actions

* Building with different JDK's (8,11,13,14)

* Building on different platforms Linux, Windows, MacOS

* Add site generation which supports release sites (https://www.mojohaus.org/mojo-parent/) as well as snapshot state (https://www.mojohaus.org/mojo-parent/snapshot/)

  * By each build on master the site will be generated. That means also the site generation is tested (like javadoc etc.).

* Add generation of release notes which is triggered by closing milestone on GitHub.



After I have done that for mojo-parent I would like to go plugin after plugin to change the builds for each plugins as well...


WDYT? 

I would like to make it lazy consensus  VOTE within 72 h


Kind regards
Karl Heinz Marbaise

    --
    You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com.

    --
    You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
    To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/trinity-1f2ab5b3-33a5-4230-bc7c-999655df23f3-1591124400788%40msvc-mesg-gmx022.

    Reply via email to