910689 - B2G sources.xml (or <insert tool>) should state which github repos map to the repos/revisions listed

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Ed Morley [:emorley]]

In bug 910662, a commit believed to have caused the breakage has been found (https://git.mozilla.org/?p=external/caf/platform/hardware/libhardware.git;a=commitdiff;h=34c1545405fad9fd42d1e7f8aa0b997e8d139604), but I have no idea which github repo this maps back to, in order to back the offending commit out.

sources.xml (or the tool created by bug 872628) should list mappings of git.mozilla.org repos back to the github repos, so sheriffs know which of the hundreds of repos under the mozilla-b2g github account they need to clone/perform the backout on.

Comment 1

[Chris AtLee [:catlee]]

I think this is most likely due to the mapping from the remotes in the upstream manifests to their mirrors on git.mozilla.org done by b2g_build.py. We should be able to dump comments into the new manifest about the original upstream.

In this case, 'external/caf' means that the upstream repo is from codeaurora.org, not github.

Comment 2

[David Burns :automatedtester]

(In reply to Chris AtLee [:catlee] from comment #1)
> In this case, 'external/caf' means that the upstream repo is from
> codeaurora.org, not github.

Is this documented somewhere that the sheriffs can get view?

Comment 3

[Ed Morley [:emorley]]

(In reply to Chris AtLee [:catlee] from comment #1)
> In this case, 'external/caf' means that the upstream repo is from
> codeaurora.org, not github.

That I did not know, thank you! :-)

Comment 4

[Chris AtLee [:catlee]]

(In reply to David Burns :automatedtester from comment #2)
> (In reply to Chris AtLee [:catlee] from comment #1)
> > In this case, 'external/caf' means that the upstream repo is from
> > codeaurora.org, not github.
> 
> Is this documented somewhere that the sheriffs can get view?

The current mapping is in the mozharness configs. e.g. 
http://hg.mozilla.org/build/mozharness/file/default/configs/b2g/releng.py#l67

Comment 5

[Chris AtLee [:catlee]]

Do the in-tree manifests resolve this issue?

Comment 6

[Ed Morley [:emorley]]

(In reply to Chris AtLee [:catlee] from comment #5)
> Do the in-tree manifests resolve this issue?

I still find it hard to map from the git.m.o repo/revision/branch listed in the manifest, to the actual repo in github that will require a backout.

Comment 7

[Chris AtLee [:catlee]]

If we put the original repo in as an XML comment, that should help.

Comment 8

[Chris AtLee [:catlee]]

Attachment: include comments for original remote url

Comment 9

[John Hopkins (:jhopkins)]

In production.