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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/AS8PR07MB7238F3607116DE0996845D2AB8999%40AS8PR07MB7238.eurprd07.prod.outlook.com.
