[VOTE] Migration from travis to GitHub Actions

[Karl Heinz Marbaise]

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

[Stephanie Wang]

SGTM!

--
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 mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com.

--

Stephanie Wang stephwang@google.com Developer Programs Engineer BigQuery, Java

[mfried...@gmx.de]

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" <goo...@soebes.de>
Datum: 2. Juni 2020
An: mojohaus-dev <mojoha...@googlegroups.com>
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

--

[Jochen Wiedmann]

On Tue, Jun 2, 2020 at 6:43 PM Karl Heinz Marbaise <goo...@soebes.de> wrote:

> 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?

While I am generally in favour of your proposal, I'd prefer to see one
plugin migrated first, without any changes in parent.

Jochen


--

Look, that's why there's rules, understand? So that you think before
you break 'em.

-- (Terry Pratchett, Thief of Time)

[Olivier Lamy]

looks good to me to move forward

--

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 mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com.

--

Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

[Oliver B. Fischer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Hi,

I have some buildjobs based on GH Actions and mostly they work pretty well. The only problem sometimes is that they can't access Maven Central.

But I don't see a major difference to Travis.

Oliver


Am 02.06.20 um 18:43 schrieb 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 mojohaus-dev...@googlegroups.com <mailto:mojohaus-dev...@googlegroups.com>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com <https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com?utm_medium=email&utm_source=footer>.
- --
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.f...@swe-blog.net
S oliver.b.fischer
J oliver.b...@jabber.org
X http://xing.to/obf
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEU7j685HGR9cAsMGwB88X6wLziPwFAl7XFYoACgkQB88X6wLz
iPxcyw//dLDJ76MP6bZC7aAqs8VKg8YuA5SjajefNKA/SJ4MeYiWGB7iUwdi0rBu
lU5cTtR9H+djq98IOoTLFUPv+Z/EwyOSk3HjYxHw9GIUKSTFsPc91Bvh1Z72lx9z
bDLFEdXgV7nMq7wBoIchcC+ZvBnh5TdCPRwX00vmW4FjnhNV5S3D8V55wM0VNFdC
11w6eP20Suc+dbbJXtdT8PhdV2ZUH4tD99WSWG2DqAnodm0E0Qk0wQUnxrMsgUOl
UXBnw/fx/viLU4k70SVoESRvd+jPTEWZUeKyEDA0RZsBikAnHJI5qnJEqbzqFkbu
8j6vBteOEJggIVkTlUCflJxtYTrD12p2XEhU8tn5HUzWNvmSdLQF2TIyVxMz0yXh
o/zQWTIdfoKf1Y8hF4O52cDg+l+PKPADKac94796iXoBtJ0xREILhq4nfPynP9o6
ct215YbgxphDzlGdiRjTHtafCU9mKuQl+dIKqoTELWcwFG0zNFPFBojy76sAFkRU
H+fcxsTCkpfn3Z5Kc/1YOEt0+bA9jsjfMlzjqCZUseCIcqXlO9Lm/GL83E5p4yo8
jPyY77304LySTgknMBvkwsjhzs3J8pnOCyrKuUySOnmoAmOvskbmZW+NM0rrfERF
hN9SN29rqIol9Hnah6WRRaGEp5RfQ1FuU1MLyvJXD++KBAXUqlI=
=HGt2
-----END PGP SIGNATURE-----

[Karl Heinz Marbaise]

On Wednesday, June 3, 2020 at 1:06:38 AM UTC+2, Jochen Wiedmann wrote:

On Tue, Jun 2, 2020 at 6:43 PM Karl Heinz Marbaise <goo...@soebes.de> wrote:

> 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?

While I am generally in favour of your proposal, I'd prefer to see one
plugin migrated first, without any changes in parent.

What would be the advantage? Of course you can do that if you like...but I will go first with mojo-parent to upgrade a lot of plugins (https://github.com/mojohaus/mojo-parent/issues?q=is%3Aclosed+milestone%3Amojo-parent-60) and release process, changelong generation, page generation etc. furthermore I don't want to add all these plugin updates to a plugins configuration

and polluting that and afterwards cleaning up (and do the work in parent a second time)...duplicating work.

Furthermore I wan't to make releasing consistent over all plugins which will not really work if I start at the plugins level (waste of time; I don't want to waste that time I have).

Afterwards a step would be to go JDK8+ for the parent and afterwards the plugins as well...

Kind regards

Karl Heinz Marbaise

 

[Anders Hammar]

How's the release site part supposed to work? Won't releases still be done manually outside of Github Actions?

Also, every build on master cannot (must not) overwrite the site for the current (latest) release. But maybe to some kind of "staging" space?

/Anders

On Tue, Jun 2, 2020 at 6:43 PM Karl Heinz Marbaise <goo...@soebes.de> wrote:

--

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 mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com.

[Karl Heinz Marbaise]

On Wednesday, June 3, 2020 at 12:34:34 PM UTC+2, Anders Hammar wrote:

How's the release site part supposed to work? Won't releases still be done manually outside of Github Actions?

Also, every build on master cannot (must not) overwrite the site for the current (latest) release. But maybe to some kind of "staging" space?

The current state is based on the idea to keep the release process on your local machine (technically it can be changed to put on GitHub actions with the problem gpg signing artifacts and putting your key on a remote machine?; That a complete different story).

The release will be made as usual from your local machine. No change. After made a release you have to close the appropriate milestone  (which will trigger the change log generation).

So the release build will create the artifacts as well as deploy the generated site via maven-scm-publish-plugin to github pages like before https://www.mojohaus.org/mojo-parent/ and furthermore opens the option 

to run master (site generation which is deployed to https://www.mojohaus.org/mojo-parent/snapshot/). This will be done by the https://github.com/mojohaus/mojo-parent/blob/9fe14ae54e37647380c73cdb63836315deb1313e/.github/workflows/deploy.yml

Github action. So having simple solution to have snapshot state as well as release state on github pages...

Kind regards

Karl Heinz Marbaise 

/Anders

On Tue, Jun 2, 2020 at 6:43 PM Karl Heinz Marbaise <goo...@soebes.de> wrote:

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 mojoha...@googlegroups.com.

[Karl Heinz Marbaise]

On Wednesday, June 3, 2020 at 12:48:56 PM UTC+2, Karl Heinz Marbaise wrote:

On Wednesday, June 3, 2020 at 12:34:34 PM UTC+2, Anders Hammar wrote:

How's the release site part supposed to work? Won't releases still be done manually outside of Github Actions?

Also, every build on master cannot (must not) overwrite the site for the current (latest) release. But maybe to some kind of "staging" space?

The current state is based on the idea to keep the release process on your local machine (technically it can be changed to put on GitHub actions with the problem gpg signing artifacts and putting your key on a remote machine?; That a complete different story).

The release will be made as usual from your local machine. No change. After made a release you have to close the appropriate milestone  (which will trigger the change log generation).

The link to the release notes generator missed: https://github.com/mojohaus/mojo-parent/blob/9fe14ae54e37647380c73cdb63836315deb1313e/.github/workflows/release-notes.yml

[Karl Heinz Marbaise]

On Wednesday, June 3, 2020 at 5:14:20 AM UTC+2, Oliver B. Fischer wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Hi,

I have some buildjobs based on GH Actions and mostly they work pretty well. The only problem sometimes is that they can't access Maven Central.

Can you explain the part  "The only problem sometimes is that they can't access Maven Central." ? 

I've seen a lot of issues with central on travis also ...

Kind regards

Karl Heinz Marbaise

But I don't see a major difference to Travis.

Oliver


Am 02.06.20 um 18:43 schrieb Karl Heinz Marbaise:
>
> 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 mojoha...@googlegroups.com <mailto:mojohaus-dev+unsub...@googlegroups.com>.

> To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com <https://groups.google.com/d/msgid/mojohaus-dev/45b4fccb-b83e-42e3-b95c-8b498fb03cb8%40googlegroups.com?utm_medium=email&utm_source=footer>.
- --
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538

E o.b....@swe-blog.net
S oliver.b.fischer
J oliver....@jabber.org

[Karl Heinz Marbaise]

Hi,

On Tuesday, June 2, 2020 at 9:00:02 PM UTC+2, Mirko Friedenhagen wrote:

Hello Karl Heinz,

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

What in your point of view a appropriate time ?

To unsubscribe from this group and stop receiving emails from it, send an email to mojoha...@googlegroups.com.

[mfried...@gmx.de]

Hi,

I think for bigger technical decisions one week would be more appropriate, i.e. 7 days, what do you think?

Best Regards
Mirko Friedenhagen
—
Sent from my mobile

Am 04.06.20 um 18:43 schrieb Karl Heinz Marbaise

Von: "Karl Heinz Marbaise" <goo...@soebes.de>
Datum: 4. Juni 2020
An: mojohaus-dev <mojoha...@googlegroups.com>
Cc:
Betreff: Re: [VOTE] Migration from travis to GitHub Actions

Hi,

On Tuesday, June 2, 2020 at 9:00:02 PM UTC+2, Mirko Friedenhagen wrote:

Hello Karl Heinz,

while I am not against moving to GitHub actions, doing a lazy 72h consensus seems a little short for me here ☺ï¸

What in your point of view a appropriate time ?

Kind regards

Karl Heinz Marbaise  

Best Regards
Mirko Friedenhagen
—

Sent from my mobile

Am 02.06.20 um 18:43 schrieb Karl Heinz Marbaise

Von: "Karl Heinz Marbaise" <goo...@soebes.de>
Datum: 2. Juni 2020
An: mojohaus-dev <mojoha...@googlegroups.com>
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 mojoha...@googlegroups.com.
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 mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/82731816-06b7-42ae-8448-bade334a7aa8%40googlegroups.com.

[Karl Heinz Marbaise]

Hi,

based on the time which run by my assumption is that there is no objection about this? 

Kind regards

Karl Heinz Marbaise

[Anders Hammar]

When you say that for each build on master the site is built, is it published to the snapshot area? Or just built but not published? 

/Anders (mobile)

--

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 mojohaus-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/3a06a363-7413-47bf-9cc3-a84139023ea3o%40googlegroups.com.

[mfried...@gmx.de]

Hello Karl-Heinz,

My +1, please go ahead. Right now I am unable to publish the extra-enforcer-rules' site so testing the site phase is essential, so that would be great.

Best Regards
Mirko Friedenhagen
—
Sent from my mobile

Am 30.06.20 um 21:17 schrieb Karl Heinz Marbaise

Von: "Karl Heinz Marbaise" <goo...@soebes.de>
Datum: 30. Juni 2020
An: "mojohaus-dev" <mojoha...@googlegroups.com>
Cc:
Betreff: Re: [VOTE] Migration from travis to GitHub Actions

--

[Arnaud Héritier]

+1

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/trinity-5082d667-ba04-4f56-9dd5-0066a88517ca-1593578917012%40msvc-mesg-gmx121.

--

Arnaud

[Karl Heinz Marbaise]

The master build will always published to the site /snapshot to separate the release and the master state...

Kind regards
Karl Heinz Marbaise

To unsubscribe from this group and stop receiving emails from it, send an email to mojoha...@googlegroups.com.

[Anders Hammar]

Great, sounds good to me then. 

/Anders (mobile)

To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/15c001ac-36a1-4cdf-93a8-05a82a3ac5edo%40googlegroups.com.

[Karl Heinz Marbaise]

Hi, will try several plugins with the new parent (60-SNAPSHOT) locally before I will finally make a release cause I expect that I find things which do not work.

So don't be astonished that I open issues related to mojo-parent upgrade an issue...on several mojo haus projects...

Kind regards

Karl Heinz Marbaise

On Tuesday, June 2, 2020 at 6:43:25 PM UTC+2, Karl Heinz Marbaise wrote:

[mfried...@gmx.de]

Hi Karl Heinz,

no worries, better CI support is great to have.

Best Regards
Mirko Friedenhagen
—
Sent from my mobile

Am 05.07.20 um 22:08 schrieb Karl Heinz Marbaise

Von: "Karl Heinz Marbaise" <goo...@soebes.de>
Datum: 5. Juli 2020
An: "mojohaus-dev" <mojoha...@googlegroups.com>
Cc:
Betreff: Re: [VOTE] Migration from travis to GitHub Actions

--

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 mojohaus-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/611e3cc4-fea7-4c4d-a70d-b72f3aa1cb3co%40googlegroups.com.

[joerg.h...@googlemail.com]

Hi there,

any updates on the status of this?

In other OSS projects, I have fully automated builds with encrypted credentials so no local build is required and side-effects are prevented (from local interference, dirty repos, file locks, OS differences with Windows vs. Linux).

With mojohaus the release build is extra-ordinary tricky and full of manual steps so if you only have to do it once a year, you will suffer each time as you forgot the magic tricks.

Yes, there are instructions how to do it but they never worked for me as documented.

Further, travis build is already broken for several plugins as Java 1.7 and 1.8 are unsupported:

Expected feature release number in range of 9 to 16, but got: 8 The command "~/bin/install-jdk.sh --target "/home/travis/oraclejdk8" --workspace "/home/travis/.cache/install-jdk" --feature "8" --license "BCL"" failed and exited with 3 during .

I did not yet get the real benefits of moving from travis to github actions. I see much more potential by improving the build and process itself by simplification and automation.

BTW: I also tried github actions with github packages and after many days wasted, I figured out with the github support, that github packages ignored maven repository conventions (e.g. SNAPSHOTS do not work at all, etc.) and created something that is more or less not working for the maven ecosystem...

However, I am happy for all kind of improvements and as long as it works properly (and is tested with a first plugin before migrating all of them at the same time as already suggested by Jochen).

Cheers

  Jörg