Closed
Bug 890086
Opened 12 years ago
Closed 12 years ago
Need a script to report all commits which have been made between two arbitrary sources.xml
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgriffin, Assigned: jgriffin)
References
Details
Sheriffing B2G is hard because B2G builds are the product of so many repos, most of which we aren't explicitly tracking in TBPL. To help address this, we should make a Python script which can take two sources.xml, and report all the commits made on all the repos between those two snapshots.
This would help sheriffs (and anyone doing bisection) understand what's changed between two builds, which is especially useful when something breaks and that bustage doesn't appear to be related to gecko.
Eventually, this tool could be hooked up to treeherder in order to provide an automatic view of such commits.
Comment 1•12 years ago
|
||
I think it would be super cool if we wrote this as an hg extension such that 'hg diff -r <rev>' would look for and download the sources.xml of <rev> and compare it to the sources.xml of <tip> (only if a special flag is passed or something) and format the output in a familiar way.
Actually, come to think of it we should just write the script as a module first and then it would be simple for an hg extension to consume it later on.
Comment 2•12 years ago
|
||
We discussed on irc putting this in mozbase, possibly in a module called mozversion:
http://logbot.glob.com.au/?c=mozilla%23ateam&s=3+Jul+2013&e=3+Jul+2013&h=mozversion#c631694
Assignee | ||
Comment 3•12 years ago
|
||
Functional but incomplete WIP: https://github.com/jonallengriffin/sourcesdiff
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → jgriffin
Assignee | ||
Comment 4•12 years ago
|
||
This is done; enhancements can be made in follow-ups.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•