Closed Bug 1486771 Opened 7 years ago Closed 6 years ago

Migration from travis-ci.org OAuth -> travis-ci.com GitHub App

Categories

(mozilla.org :: Github: Administration, task)

Product:
mozilla.org
Component:
Github: Administration
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Pike, Unassigned)

References

Details

We probably have many repos using travis-ci.org, that are now requested to move to the GitHub App on travis-ci.org. Can we do something centrally for the mozilla org (and siblings?) Didn't find an existing bug, so filing one.
:Pike - Do you have a timetable for when this is required? Depending on how soon that is, we may (or may not) have time to accommodate. (Or some other owner will need to step in.)
Flags: needinfo?(l10n)
Per https://developer.github.com/changes/2018-04-25-github-services-deprecation/: May 31, 2018: Submit your intentions for migrating or replacing your GitHub Service. October 1, 2018: GitHub discontinues allowing users to install services. GitHub Services will be removed from the GitHub.com UI. January 31, 2019: GitHub stops delivering installed services' events on GitHub.com. https://docs.travis-ci.com/user/open-source-on-travis-ci-com/ says that we should be able to let travis do something, but I'm a bit at a loss what that means for orgs of our size. Maybe contact support there?
Flags: needinfo?(l10n)
Just to note, I'm currently contacting Travis CI's support to ask them about any updated schedule and some other questions about signing in to travis-ci.com. Will report back when I hear something.

This is what I received from their support:

We can start migrating your repositories right now however history and CRON jobs won't be migrated over with the repository.

The permissions allow us to access the private repositories if needed however you still are in control of which repositories we actually have access to. When you go to your profile https://travis-ci.com/profile/org-name and click on "Manage Repositories on GitHub", if "All Repositories" is selected we can see everything but if you enter in repositories manually through the "Only select repositories" option, we will only be able to see those ones.

Unfortunately no timescale currently.

On the permissions front it is a little unclear about what exactly happens.

My non-owner account is not associated with any Mozilla private repos. So, what I'm thinking about is:

  • Un-archive mozilla/example-addon-repo
  • check Travis still works on it.
  • Ask TravisCI support to migrate it.
  • Sign into travis-ci.com with my non-owner account.
  • Take a look at if we're likely to get any issues with the permission differences.

That will hopefully give us enough info to make a decision going forward.

Thoughts welcome!

Ok, I forgot mozilla/example-addon-repo didn't actually use Travis. So I don't think I've got any options for repositories I can quietly test with.

What I can say, is that I set up a new repository just now, and I didn't need to log into Travis to do that. What I don't know is if you'd need to give them lots of access to do simple things like rebuilds.

Report from #GitHub (irc):

14:50 <jwhitlock> Our TravisCI integration stopped working in the last 24-48 hours
14:51 <jwhitlock> TravisCI s migrating from GitHub services to webhooks - https://changelog.travis-ci.com/migrating-from-github-services-to-webhooks-86328
14:52 <jwhitlock> I had to go to the website, go to https://travis-ci.org/mozilla, and click an "authorize" button
14:52 <jwhitlock> and again for https://travis-ci.org/mdn
14:52 <jwhitlock> I then closed and re-opened PRs to get the builds started
14:53 <jwhitlock> you may need to do the same for your repos, and keep an eye on your github integrations this month

I've checked our add-ons repos under the mozilla org and they look to have been migrated off the service to webhooks. This appears to be completely independent of the travis.com migration. I think this means we don't need to ask for early migration on the basis of the Github Services shutdown at the end of January.

Caveats in comment 6 still apply though. I expect intervention might be needed if for some reason Travis is unable to create the webhook to replace the service.

I think the next step here needs to be to approve the Travis CI GitHub app for the Mozilla org (https://github.com/apps/travis-ci/installations/new), which will allow new projects to at least start using it.

Then for existing open source projects, there is now a beta migration process documented here:
https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/#existing-open-source-repositories-on-travis-ciorg

I've enabled Travis on Mozilla - on a per-repository basis.

A repo admin from each repo desiring to continue to use travis will need to request access for their repos.

Thank you for enabling that. However the Mozilla org still doesn't appear in the org list on:
https://travis-ci.com/account/repositories

I believe this is because that part of Travis.com still uses the oauth app, and the travis.com oauth app is denied for the Mozilla org. There are two separate oauth apps for travis.com vs travis.org - is the latter approved and the former not?

no further issues reported, thus inferring we're good here

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.