-
Notifications
You must be signed in to change notification settings - Fork 77
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
MPS CI relies on slow and expensive Travis CI #109
Comments
I briefly investigated Amazon AWS for CI. I tried following the example at GitHub pull request and webhook filter sample for CodeBuild but under "Operating system" the only choices are "Amazon Linux 2", "Ubuntu", and "Windows Server 2019". No FreeBSD. There does not seem to be a selection of processor architectures. The CodeBuild FAQ does not even mention a C toolchain. The other DevOps products from Amazon are layers on top of CodeBuild. So at least at first glance it looks as if CI using AWS would require us to create or find a bunch of glue code to kick off EC2 images, collect results, etc. |
See also https://cirrus-ci.org/pricing/ |
Thanks. I see Apple Silicon on the list, which could be very handy. There's also big list of CI services at https://github.com/ligurio/awesome-ci |
Reopening this issue because even our remaining Travis CI builds (FreeBSD and arm64) are looking doubtful and we need redundancy at least. (Also, we have arm64 pull requests I want covered!) |
Since Travis CI have gone commercial:
GitHub now provides CI.
However:
We could use both. We should maintain a connection with Travis CI to avoid dependency on GitHub.
The text was updated successfully, but these errors were encountered: