1139024 - Switch vcs2vcs syncing off of having git.m.o be the RoR

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Justin Wood (:Callek)]

So as discussed at yesterdays group-wide meeting, it would be swell to no longer use git.m.o as the Repository of Record, and instead use github.

(At least for any repo where github is currently a mirror)

The concern raised by catlee:

* The deployment strategy must be manual and not allow any arbitrary code to be run direct from github.

The following repos are all RoR at git.m.o and mirrored to github, and have a deployment strategy that is ok for this change:

* https://git.mozilla.org/?p=build/relengapi.git
  --> http://github.com/mozilla/build-relengapi
* http://git.mozilla.org/?p=build/slaveapi.git
  --> <new repo!> http://github.com/mozilla/build-slaveapi
* https://git.mozilla.org/?p=build/tooltool.git
  --> https://github.com/mozilla/build-tooltool

(we still want github -> gitmo mirroring for all of the above)

---

Unable to presently move for not meeting the concern by catl.lee

* https://git.mozilla.org/?p=build/fwunit.git
  --> https://github.com/mozilla/build-fwunit

All other repos listed at https://wiki.mozilla.org/ReleaseEngineering/Repositories currently are either RoR at hg.m.o (and we're not changing that with this bug) or already RoR at github

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

I'm happy keeping fwunit as-is for now.  That repo only contains the application code, which is no longer very actively developed, so going to a static (wheel) deployment is an alternative, but why do extra work when you can just do nothing?

Comment 2

[hwine]

Moving to correct product/component.

Questions:
1. who is point on releng for the cutover of each repo in comment 0?
2. how urgent is this? 2 weeks, 1 week, etc? (I may want to script it as trial of ansible)

Comment 3

[Justin Wood (:Callek)]

(In reply to Hal Wine [:hwine] (use needinfo) from comment #2)
> Moving to correct product/component.
> 
> Questions:
> 1. who is point on releng for the cutover of each repo in comment 0?

I'm happy to own cutover, including communications (once timelines are known)

> 2. how urgent is this? 2 weeks, 1 week, etc? (I may want to script it as
> trial of ansible)

Not urgent at all, but certainly warrants a finite time (considering the productivity wins)

Comment 4

[Justin Wood (:Callek)]

What are we looking at for timeline here?

Comment 5

[hwine]

for the first 3 repos in comment 0, there appears to be no business need for doing the mirroring.

per IRC chat, I'll start with slaveapi as a move to github.com/mozilla

Comment 6

[Justin Wood (:Callek)]

(In reply to Hal Wine [:hwine] (use needinfo) from comment #5)
> for the first 3 repos in comment 0, there appears to be no business need for
> doing the mirroring.

For my own thought process here, I'd like the mirroring from github->gitmo for the two following reasons:

* I expect there are docs in existence pointing at git.m.o for these repos. And want adequate time to find/update them (or at least attempt to)
** I don't have those docs handy, but will certainly help us avoid confusion if we have an up-to-date repo at the location
* I want to make pain-for-users of these repos minimal by allowing git.m.o fetching to still work short term.

I also expect 6 months down the line we can delete them from git.m.o (or at least "blank"-them and disable mirroring)

An alternative I'm ok with is if we just disable mirroring and blank them with something like:

find . -path ./.git -prune -o -exec rm -rf {} \;
echo "Content moved to github at $URL" > README.md
git commit -am "Moving RoR, without mirroring" README.md
git push gitmo

Comment 7

[hwine]

per discussion in Whistler: make relengapi RoR on github, keep mirror to hg.mozilla.org (for mxr/dxr support), delete git.m.o repo

vcs-sync changes done in:
  http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/5653fc095c38

and in production.

Comment 8

[hwine]

all work done, and bug 1277297 confirms it's DONE.