Re: Re: Status of migrating to GitHub actions

[mfriedenhagen]

I second that we should strive to do things similar in all mojohaus projects. Reading https://docs.github.com/en/actions/learn-github-actions/sharing-workflows-with-your-organization it seems we can share workflows across all projects of he organization. Best Regards Mirko Friedenhagen — Sent from my mobile Am 02.03.21 um 21:39 schrieb Anders Hammar Von: "Anders Hammar" <and...@hammar.net> Datum: 2. März 2021 An: mojohaus-dev@googlegroups.com Cc: Betreff: Re: Status of migrating to GitHub actions 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 On Tue, Mar 2, 2021 at 9:29 PM 'Stefan Seifert' via mojohaus-dev <mojohaus-dev@googlegroups.com> wrote: 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 -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/AS8PR07MB7238F3607116DE0996845D2AB8999%40AS8PR07MB7238.eurprd07.prod.outlook.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/CAKDUN1uEygXGXizBfbbdyiaHNuXGgf%3D%2BjRZB_RO4%3DfJa%2B%2Bdwdg%40mail.gmail.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+unsubscr...@googlegroups.com. 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.