Github actions

[aepfli]

This is just a draft and a simple idea for now

the build steps are working, it uploads to sonarqube, and it triggers correctly the build. i need to verify the deploy (or depoy :)) step, as there is a lot going on, i am not aware of, or have not tried so far. But i thought this might be useful.

Any ideas welcome

• Issues/GitHub actions aepfli/junit-pioneer#4 as an example

---

I hereby agree to the terms of the JUnit Pioneer Contributor License Agreement.

[Bukama]

Maybe @sormuras can throw an eye on it - When I remember correctly he set up the github actions for Junit but at least for his BACH project

[sormuras]

Skimmed the .yml files and commented inline.

[sormuras]

I'd only keep: 8, 11, and introduce 14 as of today.

[aepfli]

Suggested change

	java: [ 8, 9, 10, 11, 12, 13]
	java: [ 8, 11, 14]

[sormuras]

deploy, with l

[aepfli]

i am really thinking of dropping my Travis CI pr instead of this, this seems to be way easier, as nearly all configuration is takin gplace in github

1. https://github.com/junit-pioneer/junit-pioneer/actions we need to create an action here
2. we would need to provide the sonar token for the project in https://github.com/junit-pioneer/junit-pioneer/settings/secrets

and we would be done, this would be working

1. i would still remove the deployment steps for now in Github Actions as this needs more attention
2. furthermore i would deactivate the default builds in travis.yml so we do not use so many resources.

Thoughts?
@Bukama @nicolaiparlog

[Bukama]

I appreciate dropping a "3rd party" tool for better / easier integration with the plattform we already use as long as the provided functionality stays the same. This seems to be the case here.

So I would vote for building up GitHub actions parallel to Travis- When the new script works we should disable Travis and after a (short) period of time dropping this back up scenario in total.

[aepfli]

i created an own example project with the setup :) aepfli/SonarCloud-GitHubActions-Gradle-example#2 there we see all functionality and basic configuration needed

[aepfli]

as we will have githubactions for normal builds, we we only need this for the special case of "deployments" which should only happen on master