3.x Switch from Travis CI to GitHub Actions #7114
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently, Travis CI introduced a pricing model that requires OSS projects to repeatedly apply for "free build credits". After consulting the internet, I decided to switch to GitHub Actions.
GitHub Actions (GHA) uses a build system similar to Travis CI but their setup is slightly different and the logic in
.travis.yml
and in various other files have to be converted to it.This PR introduces 4 actions depending on how the project is interacted with:
3.x
, used by dependabot or temporary branches.The latter two require secret information such as login credentials to Bintray, Sonatype and GitHub itself (for Javadocs pushback) and these have to be specified on the project's secrets page:
BINTRAY_USER
(snapshot deploy)BINTRAY_KEY
(snapshot deploy)SONATYPE_USER
(release deploy)SONATYPE_PASSWORD
(release deploy)JAVADOCS_TOKEN
(used for pushing back the generated snapshot/release javadocs togh-pages
)Unfortunately, to verify these actions, I have to merge stuff into
3.x
to trigger snapshot and do an release candidate to trigger the release.