982662 - Mirror upstream Bugzilla to github

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, defect)

Description

[Mark Côté [:mcote]]

We'll also need the upstream Bugzilla and qa directories mirrored to github:

git.mozilla.org/bugzilla/bugzilla.git to github.com/bugzilla/bugzilla.git
git.mozilla.org/bugzilla/qa.git to github.com/bugzilla/qa.git

I believe I'll need git.mozilla.org's public key to add to the GitHub repos.

Comment 1

[hwine]

Just to keep you confused, mirroring is handled by RelEng -- moving to correct product, component.

(In reply to Mark Côté ( :mcote ) from comment #0)
> We'll also need the upstream Bugzilla and qa directories mirrored to github:
> 
> git.mozilla.org/bugzilla/bugzilla.git to github.com/bugzilla/bugzilla.git
> git.mozilla.org/bugzilla/qa.git to github.com/bugzilla/qa.git
> 
> I believe I'll need git.mozilla.org's public key to add to the GitHub repos.

Ah, I didn't realize you were mirroring outside of the mozilla/ account. Not a technical problem, but we'll need to coordinate on some things. Let me think those issues through a bit.

Comment 2

[hwine]

Pushing to yet another github account is doable technically on the
legacy and future systems.  However, it does raise a question of key
management for "other" accounts.

Currently, we (RelEng) has admin access to the account of every non-Moco
repository we push to (github & bitbucket). That access is needed for 3
primary cases:
 - initial setup of push
 - trouble shooting of issues
 - update of push keys if needed

Not having admin access pretty much implies a lower SLA, as coordination
will take time. Having yet-another-admin-account is also not desirable.
There are two strategies I see:
 - require admin access to any account we push to
 - supply the public key to be added to the account, and leave the
   account admin responsible for taking the lead on any debugging

I'll defer to the folks setting up the new system as to which approach
they wish to support -- need info'd.

Comment 3

[Aki Sasaki (not active)]

a) git->git on new vcs-sync isn't supported yet, but is hopefully not too difficult to add.  We do have a large backlog of high priority items to do, though, so it may be a while before we can get this request out of legacy vcs-sync.
b) Write access without admin is ok as long as we have a flexible SLA.  Normal behavior should be fine with write, but problem-solving may involve pinging an admin, which could take significantly longer.

Comment 4

[Mark Côté [:mcote]]

Thanks, this is good feedback.  Admin access is probably okay, but then again so is a relatively flexible SLA.  The GitHub mirror is being created for several purposes:

* Provide more exposure.
* Give access to GitHub's nifty tools.
* Enable us to use travis-ci, which lets us get off of tinderbox.

Only the third one would really be particularly affected by mirroring latency.  If we're talking occasionally a few hours, I should think that's okay, at least at the current rate of commits.  If we're talking days, that's much less ideal.

Flagging other Bugzilla project leads for opinions.

Comment 5

[hwine]

To clarify the SLA issue -- we're discussing the SLA for initial setup, troubleshooting, and credential changes. That is, one time or very rare events. We're just striving for "no future surprises" here, since you the first customer for this usage pattern.

Normal operations are quite stable after initial configuration, and latency between the master and mirror are not impacted. I.e. we want to get you off tinderbox :) 

We're currently mirroring over 450 repositories between various git servers, and haven't needed admin access since the setup of the first mirror.

Comment 6

[:glob ✱]

my main concern here is the timing -- aki's comment indicates this won't be happening any time soon :(

mcote - we already have a script which mirrors our git repo to bzr; maybe we should just extend it to also push changesets to github until vcs-sync is ready?

Comment 7

[Mark Côté [:mcote]]

I am confused by new vs legacy vcs-sync.  aki, are you saying that new repos, such as the bugzilla & bmo ones, use the new vcs-sync which currently lacks this mirroring feature?  Or can they be set up with the legacy system?  In short, what would be an ETA on getting these repos mirrored to GitHub?

Comment 8

[hwine]

Sorry for the confusion on the legacy-vs-new -- I can address that. We _will_ bring this up on the legacy system. And that can be pretty darn soon -- just have to get things 

The reason to raise the legacy-vs-new here was to ensure the transition to new would be transparent to you. I.e. I'll make legacy behave the way the new system will.

I believe the concerns in comment 4 and comment 7 have been addressed, and we're ready to proceed. I'll be in touch with :mcote this week about getting the key installed in your github account

Comment 9

[hwine]

deployed via http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/1ea37a838af0

For the following repositories:
https://git.mozilla.org/bugzilla/bugzilla.git -> https://github.com/bugzilla/bugzilla.git
https://git.mozilla.org/bugzilla/qa.git -> https://github.com/bugzilla/qa.git

https://git.mozilla.org/webtools/bmo/bugzilla.git -> https://github.com/mozilla/webtools-bmo-bugzilla.git
https://git.mozilla.org/webtools/bmo/qa.git -> https://github.com/mozilla/webtools-bmo-qa.git

Comment 10

[Pete Moore [:pmoore][:pete]]

Nice work Hal. :)

Comment 11

[Mark Côté [:mcote]]

Seem to be working great, so I'll close this out.  Thanks!