-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move from Travis CI to GitHub actions #408
Comments
Is there a brief explanation anywhere of the advantages? |
For my own future reference, I think resource limitations on Travis CI are a good enough reason to move. Also, switching to GitHub Actions will let us easily run tests on Windows. |
Travis CI is still the better and is being used my many big organisations however i would like to work on this if you give me a go ahead cc @msridhar @lazaroclapp |
Thanks for the offer, @sherrif10! But, I think it will be easier for a maintainer still at Uber like @lazaroclapp to take care of this one, as it requires dealing with permissions to set up GitHub Actions, adding credentials to set up snapshot build uploading, etc. |
This change sets up GitHub Actions as a parallel build CI to Travis (for now). GitHub Actions should build NullAway on MacOS X and Linux using JDK 8 and JDK 11, and on Windows using JDK 8. Additionally, this migrates snapshot uploading and coverage tracking to GitHub Actions, disabling the equivalent Travis CI events as they will likely conflict. This also switches the Gradle plugin we were using for code coverage support and re-enabled coverage uploads to Coveralls (from GH Actions). Finally, this includes a few tooling dependency upgrades, most notable an upgrade of the Android SDK and build-tools used to build this repo to v30. See #408
Probably worth doing when possible, as per @tyvsmith's advice 馃榿
The text was updated successfully, but these errors were encountered: