-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
ci(github): Reimplement CI in GitHub Actions #634
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci(github): Reimplement CI in GitHub Actions #634
Conversation
Part of #627, sets us up for expanding the OS matrix we test against.
|
Ready for review, @BYK et al. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just brilliant 🎇
Thank you so much for doing this!
|
GHA has been quite stable for some other things so I think it should be safe to remove Travis and see if we can make this even better. Maybe separate install and actual test steps? I don't know if we can leverage any caching easily as you indicated but why not try? |
| @@ -0,0 +1,33 @@ | |||
| name: test | |||
| on: push | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh wait, this will only run on branch pushes. We should also add pull_request for this to be a proper commit check, right @chadwhitacre?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, good call. Maybe #639 does what we want?
This is a fairly wooden port of the Travis CI config to GitHub actions. Note that this doesn't remove Travis yet. I figure we should run both in parallel for a bit to make sure GitHub Actions is trustworthy. E.g., there might be some caching we want to do to speed up the build, I didn't look into that yet.
Presumably there's some button clicking that needs to happen before this'll run in the main repo. Here's a good run in my fork:
https://github.com/chadwhitacre/onpremise/runs/998127947
And here's a sample bad run in my fork, showing that test failures indeed break the build:
https://github.com/chadwhitacre/onpremise/runs/998137076
Part of #627.