865282 - Mirror github.com/apitrace/apitrace to git.m.o

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Vasil Dimov [:vd]]

Please mirror:

git://github.com/apitrace/apitrace.git

to

https://git.mozilla.org/external/github/apitrace/apitrace.git

It is needed for Bug 831147 - Integrate apitrace into build

Comment 1

[Vasil Dimov [:vd]]

Then adding an entry like:

--- cut ---
diff --git a/configs/b2g/releng-eng.py b/configs/b2g/releng-eng.py
--- a/configs/b2g/releng-eng.py
+++ b/configs/b2g/releng-eng.py
@@ -84,10 +84,11 @@ config = {
     "repo_remote_mappings": {
         'https://android.googlesource.com/': 'https://git.mozilla.org/external/aosp',
         'git://codeaurora.org/': 'https://git.mozilla.org/external/caf',
         'https://git.mozilla.org/b2g': 'https://git.mozilla.org/b2g',
         'git://github.com/mozilla-b2g/': 'https://git.mozilla.org/b2g',
         'git://github.com/mozilla/': 'https://git.mozilla.org/b2g',
         'https://git.mozilla.org/releases': 'https://git.mozilla.org/releases',
         'http://android.git.linaro.org/git-ro/': 'https://git.mozilla.org/external/linaro',
+        'git://github.com/': 'https://git.mozilla.org/external/github',
     },
 }
--- cut ---

in http://hg.mozilla.org/build/mozharness/configs/b2g/releng-eng.py would be sufficient to have these in the manifests (ie https://github.com/mozilla-b2g/b2g-manifest/blob/master/emulator.xml):

<remote name="github" fetch="git://github.com/"/>
...
<project path="external/apitrace" name="apitrace/apitrace.git" remote="github" revision="master"/>

Comment 2

[hwine]

Note that to match conventions on the existing repositories, the repository will be
  git.mozilla.org/external/apitrace/apitrace.git

Again to match conventions, the manifest changes should refer to a 'remote' of 'apitrace' with a fetch of 'git://github.com/apitrace/'

Please wait for this bug to close before submitting the new manifest changes - that's when all the machinery will be operational.

Comment 3

[Vasil Dimov [:vd]]

Ok, acknowledged. I chose a generic remote with fetch='git://github.com/' because that way if new projects, hosted on github, are to be added later, they can be added without adding a new remote to the manifests.

Comment 4

[hwine]

Repo is now mirrored. Please go ahead with manifest changes using a remote name of 'apitrace'.

(mirror config via http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/11cbd22a4f54 deployed to all production hosts.)

Comment 5

[hwine]

Attachment: add remote 'apitrace'

Comment 6

[hwine]

Attachment: add remote 'apitrace'

Comment 7

[hwine]

Comment on attachment 743769 [details] [diff] [review]
add remote 'apitrace'

checked in:
  https://hg.mozilla.org/build/mozharness/rev/30b10e6307aa
merged to production:
  https://hg.mozilla.org/build/mozharness/rev/ba087e77749f

Comment 8

[Vasil Dimov [:vd]]

Hi,

How often is the repository synced? Can I check somehow whether a latest push upstream has been synced already?

Comment 9

[Vasil Dimov [:vd]]

For some reason I thought that the mirrored repository is not public, while it actually is (of course!).

I just cloned https://git.mozilla.org/external/apitrace/apitrace.git and checked that the changeset that I am interested in has already been mirrored.

Still, out of curiosity, how often is the repository synced?

Comment 10

[hwine]

You should see a change propagate within about 20 minutes. The actual time depends on load, other changes, etc.

You can also check the web view at https://git.mozilla.org/?p=external/apitrace/apitrace.git;a=summary to look for a particular changeset.