-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Migrate testing to travis-ci.com and use the new Checks API #1551
Comments
For what it's worth, I think the migration for the Travis builds will be automatic. I just created an account on travis-ci.com to migrate my current projects, and for the projects that were already on travis-ci.org I have this message :
|
We just need to update a few URLs in a few days after the migration option comes up. |
ALE now uses travis-ci.com. I got into the beta today, and I just finished migrating it over. |
https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps
travis-ci.org will stop working eventually. We should switch to using travis-ci.com when we can, before they shut the old domain down. The domain will stay up for a while, but it will be nice to switch to the new as soon as we can.
The following was also announced.
https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/
https://blog.travis-ci.com/2018-05-07-announcing-support-for-github-checks-api-on-travis-ci-com
We should see if we can set up the Vader tests, Vint, and the custom checks with the newer Checks API, to provide very good information about what went wrong in tests. AppVeyor will probably catch up later, so we should consider getting that to use Checks for Windows test later too.
The text was updated successfully, but these errors were encountered: