Today’s the day where GitHub finally deprecated “services” in favor of GitHub Apps.
Seems like we’re still using travis CI ‘service’ instead of the GitHub App.
There’s a write up here, where an admin need to configure and allow travis CI GitHub App to be installed.
I’m not sure what to do from here unfortunately. The documentation notes an “Activate and Migrate” button that doesn’t seem to exist. I’ll email Travis CI support and CC you @Mariatta
Travis’s messaging about this has been really bad. I guess being acquired last week probably doesn’t help. They finally posted a new update today.
The original plan they announced is to move everyone from .org → .com, but the tool for that is still in “private beta”. There’s an email address you can contact to get into the beta, but it looks like they just didn’t get this together in time.
Instead, a few weeks ago they started going through all the repos that were using the “service”, and using their credentials to also configure a “webhook”. If you go to https://github.com/python/cpython/settings/hooks and see an entry for notify.travis.org, then I think that means that the repo has been migrated and everything should keep working. (And presumably at some point in the future there will be another migration, to get to travis-ci.com and our glorious App-alicious future.)
Their latest announcement says that most projects don’t need to do anything at all:
For the majority of your repositories, this transition has gone smoothly without any issues. On your end, you will not need to take any action and you’re good to go as if nothing changed! – Blog – Travis-CI
@Mariatta it appears that the org => com thing just isn’t happening at this point. If we’re getting builds, I think we should just hang tight and await what Travis does on that front next.
I wonder if this is also why a few weeks ago it appeared that several readthedocs projects stopped being updated? I had to fix this for mypy, and IIUC Benjamin had to fix this for six; I vaguely recall another.
Ok I think I understand this now…
Indeed they’re not using GitHub “service” anymore, but travis has added the webhook to our repos. Builds are still happening, via webhooks to travis-ci,org.
At this point, perhaps nothing we need to do here, other than removing the travis-ci service from our GitHub repos? (check first that the webhook exists).