Status of migrating to GitHub actions
37 views
Skip to first unread message
Stefan Seifert
Mar 2, 2021, 3:29:28 PM3/2/21
to mojoha...@googlegroups.com
i've seen a few mojohaus projects already migrated from travis to GitHub actions.
this is important because travis-ci.org quickly degenerates and will be switched off in a few weeks (following the message on their website). travis-ci.com is a possible replacement, but they are limiting build time for OSS projects (unless you get an exception by their management).
i would like to migrate the build-helper-maven-plugin [1] to GitHub actions and created a branch with a copy of the scripts from versions-maven-plugin [2]. this is working quite well. other plugins like animal-sniffer-plugin use a completely different set of workflow scripts [3], and it is still using travis in parallel.
is there an "official way" planned to be used for all mojohaus plugins, it should every plugin just go the easiest way that fits for their purposes?
the workflow scripts from versions-maven-plugin limit their builds to branches matching '*', which are all branches that do not contains a "/" [4]. this looks like a strange restriction for me, probably that was not the intention.
stefan
[1] https://github.com/mojohaus/build-helper-maven-plugin
[2] https://github.com/mojohaus/versions-maven-plugin/tree/master/.github/workflows
[3] https://github.com/mojohaus/animal-sniffer/tree/master/.github/workflows
[4] https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#patterns-to-match-branches-and-tags
this is important because travis-ci.org quickly degenerates and will be switched off in a few weeks (following the message on their website). travis-ci.com is a possible replacement, but they are limiting build time for OSS projects (unless you get an exception by their management).
i would like to migrate the build-helper-maven-plugin [1] to GitHub actions and created a branch with a copy of the scripts from versions-maven-plugin [2]. this is working quite well. other plugins like animal-sniffer-plugin use a completely different set of workflow scripts [3], and it is still using travis in parallel.
is there an "official way" planned to be used for all mojohaus plugins, it should every plugin just go the easiest way that fits for their purposes?
the workflow scripts from versions-maven-plugin limit their builds to branches matching '*', which are all branches that do not contains a "/" [4]. this looks like a strange restriction for me, probably that was not the intention.
stefan
[1] https://github.com/mojohaus/build-helper-maven-plugin
[2] https://github.com/mojohaus/versions-maven-plugin/tree/master/.github/workflows
[3] https://github.com/mojohaus/animal-sniffer/tree/master/.github/workflows
[4] https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#patterns-to-match-branches-and-tags
Anders Hammar
Mar 2, 2021, 3:39:50 PM3/2/21
to mojoha...@googlegroups.com
There is no "official" mojohaus way that I know of. But I don't see any benefit of every mojo doing it differently so I anyone that want to create one common solution could do it.
/Anders
--
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/AS8PR07MB7238F3607116DE0996845D2AB8999%40AS8PR07MB7238.eurprd07.prod.outlook.com.
Olivier Lamy
Mar 2, 2021, 4:37:17 PM3/2/21
to mojoha...@googlegroups.com
no official way for sure but they will look very similar at the end :)
But as far I can see we do not need both action in versions-m-p.
And BTW I would prefer using matrix rather than duplicating lines such these https://github.com/mojohaus/versions-maven-plugin/blob/master/.github/workflows/main.yml
cheers
--
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/AS8PR07MB7238F3607116DE0996845D2AB8999%40AS8PR07MB7238.eurprd07.prod.outlook.com.
mfried...@gmx.de
Mar 3, 2021, 5:04:53 PM3/3/21
to mojoha...@googlegroups.com
Olivier Lamy
Mar 3, 2021, 6:34:05 PM3/3/21
to mojoha...@googlegroups.com
sounds good. I already created this https://github.com/mojohaus/.github/tree/master/.github for release-drafter maybe we can extend to actions as well
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/trinity-7915fcba-f15b-4bb1-a4c5-b5d23a19e8e1-1614809091634%40msvc-mesg-gmx023.
joerg.h...@googlemail.com
Jun 8, 2021, 10:43:38 AM6/8/21
to mojohaus-dev
Hi there,
thanks, Oliver, for creating the template. I just created the action for servicedocgen from the templated and it works like a charm:
I am enabling GHA check for PRs and then will remove travis.
Cheers
Jörg
Benjamin Marwell
Jun 8, 2021, 11:34:17 AM6/8/21
to mojoha...@googlegroups.com
Hi,
I created a github build Workflow with matrix for both aspectj-maven-plugin and the mojohaus site.
The idea is to build one JDK first and only the matrix if it succeeds. This will help keep free slots for other Mojohaus projects. Concurrent Workflows are limited per organisation.
HTH
Ben
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/bf981011-7992-48d8-9008-ad378c897048n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages