-
Notifications
You must be signed in to change notification settings - Fork 569
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
Consider migrating from Travis-CI to Github Actions #2208
Comments
I'd personally be wary of integrating too much into Github. The main reason (of course) is that Github is now owned by Microsoft. Yeah, they've been better to the OSS community recently, but I still don't trust them, and if we have to jump ship for whatever reason, the fewer disruptions, the better. |
Any particular reason we couldn't use both? It would give us more redundancy if Travis CI goes down. |
Sure we can use both. In case we have to jump ship it will break everything anyway. We may consider to create mirror (read-only) on gitlab. |
Tried that previously -- IIRC it works well. 😄 |
We'll use both of them. TravisCI runs on Ubuntu 14.04, maybe we can get something newer from these guys. The test in Travis covers about 55% of the code (this is the number from 6 months ago), if we get a newer kernel we can bump up the coverage. |
Let's move the discussion over to #2729. |
Github Actions is new service (beta) for CI. Perhaps it has better intergration than third party services and maybe more features.
The text was updated successfully, but these errors were encountered: