Closed Bug 1366052 Opened 8 years ago Closed 8 years ago

move socorro from mozilla to mozilla-services github org

Categories

(Socorro :: General, task)

Product:
Socorro
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: willkg, Unassigned)

Details

The mozilla-services org pays for CircleCI and has some other niceties. Further, all Socorro things that are run by Ops should get moved to the mozilla-services org. (There are probably other good reasons as well.) Because of that, we should move mozilla/socorro to mozilla-services/socorro.
This was pretty straight-forward for Antenna and socorro-pigeon. It shouldn't be a big deal for Socorro. Maybe we should do this next week? One of the reasons we'd want to move is that we're redoing the Socorro infrastructure to use Docker, CircleCI, and a different AWS account. Because mozilla-services pays for CircleCI, we'd get the advantages of that.
There are a lot of external clones, installs, etc. If we do this move... how effective are redirects?
As far as I've seen, everything to mozilla/socorro will get redirected to mozilla-services/socorro. Github transfers are pretty magical. Having said that, maybe we should make a list of things we're concerned about and then see if equivalent things work with Antenna which was just transferred? Here's everything I can think of: * PR links * https://github.com/mozilla/socorro/pull/3786 * links to code files * https://github.com/mozilla/socorro/blob/master/docker/README.rst * https://github.com/mozilla/socorro/blob/ea43c233c613d99d5c0bb2a3ef07a8283d060c6d/docker/README.rst * tarball links * https://github.com/mozilla/socorro/archive/master.tar.gz * https://github.com/mozilla/socorro/archive/272.tar.gz What other kinds of links are we concerned with?
I'd be concerned about clones, and the fact that we will all have to update our upstream URLs. But I guess there's no way around that?
Clones/forks should continue to work just fine because of the redirects. We can update upstream urls at our leisure, but I'll probably do all the ones in the repo all at once. Are there other kinds of links we're concerned about? If not, I'll go through the ones I listed in comment #3 and make sure equivalent ones all work with Antenna which was just moved.
✅ PR links ✅ links to code files ✅ tarball links work I think that's everything I was concerned with. +1
Rather, I tested that all of those types of things redirected correctly from mozilla/antenna to mozilla-services/antenna
Arrr. It be done.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
for posterity -- this broke treeherder links, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1378117 I don't think there's anything for us to do here.
Per https://bugzilla.mozilla.org/show_bug.cgi?id=1378117#c5, the problem was that treeherder has an allow list that had the old repository url, but not the new one, and that it ignores whatever from urls it doesn't recognize. I don't know what treeherder does with Socorro, so I'm a bit surprised. But even if I did, maybe there are allow lists we don't know about out there. Generalizing the issue, I think any time someone moves a repo from one github org to another at Mozilla, they need to announce the move. I have no idea what form that should take or what the best way to notify people would be. Is there a good channel for that kind of information? Maybe a blog post that ends up on planet? Maybe an email to some list? Maybe some other channel? Maybe all of those?
Aha! It's for QA reporting e2e CI information. You can see the data here: https://treeherder.mozilla.org/#/jobs?repo=socorro I sent out a (belated) notice to socorro-dev. That should cover us.
You need to log in before you can comment on or make changes to this bug.