Closed
Bug 606630
Opened 14 years ago
Closed 5 years ago
Human readable build dates
Categories
(Socorro :: Webapp, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dmandelin, Assigned: willkg, Mentored)
Details
Attachments
(1 file)
Socorro identifies the browser for a crash using a "Build ID" field. This shows up in the table view, reports view, and the single report view, for example. This is somewhat lacking when dealing with versions like "4.0b8pre":
What I really want to know is:
- Is this one of our official nightly builds?
- If so, which one is it? mozilla-central, tracemonkey, etc?
- What date was it built on, in an easy-to-read format like 2010-10-18,
instead of 20101018043251, which is a bit hard on the eyes.
It would also be nice to show on those pages (where appropriate), the hg rev it was built from (with link) and a link to the nightly build ftp dir.
|
||
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
|
||
Updated•13 years ago
|
Component: General → Webapp
|
|
||
Comment 1•11 years ago
|
||
This is covered by other bugs: - bug 596349 - which one is it, covered by release channel and build id That leaves human readable build date. We can do that.
Severity: normal → trivial
Summary: Display build identification more clearly in Reports view → Human readable build dates
Whiteboard: [mentor=rhelmer@mozilla.com]
|
||
Comment 2•11 years ago
|
||
Landed https://github.com/mozilla/elmo/commit/87d7e6452253395714357cc39cea1517f2f641e0
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
|
|
||
Comment 3•11 years ago
|
||
Oops! My tooling sucks. I closed the wrong bug!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
||
Updated•10 years ago
|
Mentor: rhelmer
Whiteboard: [mentor=rhelmer@mozilla.com]
|
Assignee | |
Comment 4•5 years ago
|
||
Assignee: nobody → willkg
|
|
Assignee | |
Comment 5•5 years ago
|
||
Landed in https://github.com/mozilla-services/socorro/commit/ef8d384c477f3b4065e526befda62f9ed525353f
Marking as FIXED.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•