Closed Bug 687630 Opened 13 years ago Closed 6 years ago

Link Build ID to something useful

Categories

(Socorro :: Webapp, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gps, Assigned: osmose)

References

(Blocks 1 open bug)

Details

Currently, "Build ID" shows up a number of places. Currently, it is just a regular text string e.g. '20110918030911'. I would like the Build ID to be clickable and result in something useful being displayed.

Some ideas for things to link to:

- Installer for binary that crashed
- Source repository and changeset
- tbpl for build
Is this still an issue? If so, I will need to know which of the three options I need to link these to in order to fix it on the front end.
I'd say the one of those that is easiest to get from the data we have.
Assignee: nobody → sneethling
Assignee: sneethling → nobody
Component: Socorro → General
Product: Webtools → Socorro
Component: General → Webapp
(In reply to Gregory Szorc [:gps] from comment #0)
> Some ideas for things to link to:
> 
> - Installer for binary that crashed

Since we scrape FTP to pick up information about versions and build IDs, we could quite easily link to this, I think. At least to the directory it came from.

> - Source repository and changeset

Not so sure about this - if there is a valid crash associated with it, maybe, but sometimes we link to multiple repositories in the stack.

> - tbpl for build

I think this has the same problem as above.
It would be neat if we had a webapp that tracked releases, so we could link to a release page for a specific build.
This is probably a good idea still. bwong's team has a variety of good options here. We may investigate this further in 2018H1.
I think we should link to Buildhub for now. That seems helpful. Then Buildhub can link to other relevant things like source repository and changeset and all that.

I wrote up an issue in the Buildhub tracker: https://github.com/mozilla-services/buildhub/issues/318
Making this a P3. It should be straight-forward to implement once Buildhub has urls we can use.
Priority: -- → P3
There are a bunch of related bugs, so I'm bumping this up to P2. It'd be great if we could get this done this quarter.
Priority: P3 → P2
Buildhub supports this kind of link: https://mozilla-services.github.io/buildhub/?q=20180105100137

I think we should go with that for now. We can change/improve it later as new needs/requirements pop up.
Assignee: nobody → mkelly
I went through the webapp and found what I think are all the spots where we display a BuildID:

- Signature report 
  - Aggregation tab
  - Reports tab
  - Graphs tab
- Crash report
  - Details tab
  - Metadata tab
- Supersearch (when you facet on it)

They're already links in supersearch since clicking them adds the to the search form, and I don't think I should change that.

Linkifying the build ID in the crash report is pretty easy. Doing the same for the signature report is harder. The two dependent bugs are both asking for this kind of info from the crash report, which makes me lean towards linkifying the crash report and leaving the signature report alone.

gps: Do you have any thoughts on how useful linkifying build IDs in the signature report would be? Is it useful to just focus on the crash report?
Flags: needinfo?(gps)
I don't look at crash reports very often so I don't have a meaningful opinion :(

Maybe drop in #build and ask? There are usually enough people lurking that you'll get some good opinions.
Flags: needinfo?(gps)
Commits pushed to master at https://github.com/mozilla-services/socorro

https://github.com/mozilla-services/socorro/commit/4b4355a6d92dd576df5e4a26ade578e01eda44d9
Fix bug 687630: Linkify Build ID in crash report to BuildHub.

https://github.com/mozilla-services/socorro/commit/dd63ea70af4f1532a32c29c442e0f9aefbd2be85
Merge pull request #4301 from Osmose/linkify-buildid

Fix bug 687630: Linkify Build ID in crash report to BuildHub.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.