Hi Slawomir, sorry for the late reply. Great that you see the value of the workflows. I don't think there are any strict rules or guidelines around how the workflow should be configured exactly, but I think it makes sense to have them in place. Perhaps we should also look into a way of reusing workflows in all or most of the projects (maven-core is a bit different).
Just wanted to mention that for the Apache team the Apache Jenkins server is what matters most. GA are helpful for contributors and committers working via PRs, but in the end Apache Jenkins has to pass before a merge is allowed. Hence, I think we should go for a reasonable workflow configuration, it does not have to be more extensive than the Jenkins setup. Still, having macOS builds is very useful, Jenkins does not have that AFAIK. Martin Op za 11 sep. 2021 om 20:43 schreef Slawomir Jaranowski < s.jaranow...@gmail.com>: > Hi, > > Many of maven, maven plugins projects have GutHub Action build configured. > It is very useful for contributors - we can verify PR early, especially on > many different operating systems - which can't be done locally, or is more > complicated. > > Most of workflows have define build matrix like: > > matrix: > os: [ubuntu-latest, windows-latest, macOS-latest] > java: [8, 11, 16, 17-ea] > > But some have: > > matrix: > os: [ubuntu-latest, windows-latest, macOS-latest] > java: [8, 11, 16, 17-ea] > jdk: [adopt, zulu] > > > Question: > > Are there some guidelines about how GitHub Action should be configured? > If no guidelines, which build matrix will be the most expected? > > I ask in conjunction to https://issues.apache.org/jira/browse/MDEP-768 > > > -- > Sławomir Jaranowski > > https://twitter.com/SlawekJaran > https://github.com/slawekjaranowski > https://linkedin.com/in/slawomirjaranowski >
