Closed Bug 872628 Opened 12 years ago Closed 8 years ago

Provide a link in TBPL to show the differences between two builds' sources.xml

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgriffin, Unassigned)

References

Details

In order to make problems like bug 872522 easier, we should provide a mechanism that sheriffs can easily use to see the differences in sources.xml between two B2G builds. In the above case, between the last good build in m-i and the first failing build, the differences were: 05:02:06 INFO - <project name="gaia.git" path="gaia" remote="mozillaorg" revision="ec6e4178f3227f6adac6191855072a89b6bbc6a6"/> 05:02:06 INFO - <project name="gonk-misc" path="gonk-misc" remote="b2g" revision="49469de4063a797776230194c2da019f6a4bcdbf"/> After we have the gecko-gaia coupling in place from bug 868597, this would have provided enough information to find the source of the problem, which turned out to be the above gonk-misc commit. It's possible to figure this out by comparing the logs, but since there are so many repos involved, it can be a pain. At a minimum, we should probably upload sources.xml to the public build dir (which now only contains the build log); it would be even better if we could provide some UI to automatically highlight the differences in sources.xml between two arbitrary B2G builds. Bonus points if we could automatically map the git.mozilla.org commits that buildbot uses to their original repos.
Blocks: 899969
Depends on: 910676
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.