Closed Bug 761751 Opened 13 years ago Closed 10 years ago

Provide a link to changesets from telemetry UI

Categories

(Mozilla Metrics :: Frontend Reports, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
Moved to JIRA

People

(Reporter: taras.mozilla, Unassigned)

Details

(Whiteboard: [JIRA BIV-112] [Telemetry:P2])

One of the things we often need to do is to see what changed in a particular build is to see the changeset for that build. Would be great of telemetry frontend provided a changesets link when clicking on a build id. 11:12 < jlebar|lunch> taras, What I do to get the csets is look at the build directories on the FTP server. 11:12 < jlebar|lunch> taras, There are .txt files with the cset identifiers. 11:13 < jlebar|lunch> taras, Then the pushloghtml syntax is like https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=807403a04&tochange=2db9df428 1 For example: link for June 1st build is https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=73783bf75c4c&tochange=9274e6b53af4 where changeset ids are fetched from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012-06-01-03-05-20-mozilla-central/firefox-15.0a1.en-US.win32.txt and http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012-06-02-13-43-06-mozilla-central/firefox-15.0a1.en-US.win32.txt
First of all, the build ID alone isn't enough to find the changeset IDs, so with the selectors at default this won't be possible. Looking at the example links where we can find the changeset IDs, I tried to build them using the parameters from the dashboard. Following http://ftp.mozilla.org/pub/mozilla.org/ there is "firefox", which can be get from the Application Name selector, although there are 3 options available in the dashboard, "fennec", "firefox" and "thunderbird", and in the ftp I see "firefox" and "thunderbird", don't see "fennec", or it's there with another name? Next we have "nightly", which can be get by the Application Version selector. Available on ftp is only "nightly", I think that the other directories doesn't have any information about changesets. What about release version and previous? For aurora I did found inside "nightly/latest-mozilla-aurora/" the 15.0a2 version, but no mention of the build ID, only in the txt inside we can see 20120611042006 and 20120610042007. There is also some directories that after the build ID have "mozilla-aurora" and "mozilla-aurora-debug", as far as I've seen some are for 14.0a2 and others 15.0a2, should use these ones instead of "latest-mozilla-aurora"? And for other *.a02 versions? Also in the ftp there is the directory http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2012/ and other years which has just build IDs regarding to each year, separated in directories for month, is this the same information that is on http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly? Which one should be used? Assuming that we are searching for a changeset from a build ID from "firefox" "nightly", in the ftp we can see many directories corresponding to the build ID, such as "2012-06-01-03-05-20" in the example, but it's followed by "-mozilla-central" and this part of the link varies a lot, it can be mozilla-central, mozilla-inbound, profiling, ionmonkey, oak, ux, fx-team, etc. For example, for "firefox" "nightly" "2012-06-01-04-02-28" there is "-ionmonkey" and "-oak", for each having "15.0a1" and "linux" we get the respective changesets "f55395bc4e61" and "06c193df0776". Which one is right? How can we know what comes next in the directory's name after the build ID? Is there any rule here?
Perhaps someone from releng/a-team can explain what's the right way to do this. I really have no idea who to ask. Heather? Please note that if we can't do this, we also can't do anything with the TelemetryHistograms.h file (i.e. the bugs that bug 748417 blocks, particularly bug 736189), because handling that file requires us to know what's the right hg rev. We could of course send the hg rev along with the telemetry ping.
Marking: in group of > 33 asks for Telemetry that need PM priority before triage/scheduling.
Status: NEW → ASSIGNED
Whiteboard: Telemetry -- needs PM project priority
Triaged.
Target Milestone: Unreviewed → Backlogged - BZ
Whiteboard: Telemetry -- needs PM project priority → [Telemetry:P2]
Whiteboard: [Telemetry:P2] → [JIRA BIV-112] [Telemetry:P2]
Target Milestone: Backlogged - BZ → Moved to JIRA
Pentaho histograms are all decom'd at this point.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.