Travis CI migrated from the legacy GitHub API to the new GitHub Action
Hi, tl; dr Travis CI issues are now resolved thanks to Ernest! During the last 3 months, the Travis CI job failed randomly to report the build status to GitHub pull requests: https://github.com/python/core-workflow/issues/371 I discovered that travis-ci.org uses the legacy GitHub API, whereas there is a new travis-ci.com website which uses the new GitHub Action API. The migration started in May 2018, is still in the beta phase, and must be done manually: * https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-... * https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/#existi... Two weeks ago, Ernest W. Durbin III migrated the GitHub "python" organization from travis-ci.org to travis-ci.com, and also migrated the cpython project to travis-ci.com (the migration requires to migrate each project individually). Since the migration, I didn't notice the "Travis CI doesn't report the build status" issue anymore on new pull requests. Great! Thanks Ernest! Victor -- Night gathers, and now my watch begins. It shall not end until my death.
participants (1)
-
Victor Stinner