Closed Bug 614971 Opened 14 years ago Closed 7 years ago

Specify the last changeset (and the repository?) in the "Details" table

Categories

(Socorro :: Webapp, task, P5)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mounir, Unassigned, Mentored)

Details

It might be interesting to know the last changeset used and the repository to know if the version used had a specific changeset. It might be very useful in case of self-build versions which might be outdated.
Socorro doesn't really have this data directly, it's not something we send from the client. It gets it indirectly in the source file data that comes from Breakpad, but it's possible to have multiple repositories listed there, like with Thunderbird or Seamonkey.
So it might be possible to show all repositories and related changesets if the needed informations have been sent by Breakpad?
Component: Socorro → General
Product: Webtools → Socorro
Component: General → Webapp
Not Breakpad, but this info is on the FTP server so we have it. Much harder for B2G - not sure we have a solution there yet.

"Nice to have"
Severity: normal → trivial
Priority: -- → P5
Whiteboard: [mentor=rhelmer@mozilla.com]
B2G builds do have a sources.xml file that comes out of the build containing all the repos and the changesets used, but not sure if Socorro gets that.
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #4)
> B2G builds do have a sources.xml file that comes out of the build containing
> all the repos and the changesets used, but not sure if Socorro gets that.

Socorro uses these JSON files not the XML as far as I can tell:
https://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/nightly/1.1.0/latest/socorro_hamachi.json

https://github.com/mozilla/socorro/blob/master/socorro/cron/jobs/ftpscraper.py#L79
(In reply to Robert Helmer [:rhelmer] from comment #5)
> Socorro uses these JSON files not the XML as far as I can tell:

And we only have those for Mozilla-generated builds while the most interesting build are the ones that get shipped widely, which are actually built by partners.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #7)
> (In reply to Robert Helmer [:rhelmer] from comment #5)
> > Socorro uses these JSON files not the XML as far as I can tell:
> 
> And we only have those for Mozilla-generated builds while the most
> interesting build are the ones that get shipped widely, which are actually
> built by partners.

This is true - do we have a bug tracking that?
(In reply to Robert Helmer [:rhelmer] from comment #8)
> (In reply to Robert Kaiser (:kairo@mozilla.com) from comment #7)
> > (In reply to Robert Helmer [:rhelmer] from comment #5)
> > > Socorro uses these JSON files not the XML as far as I can tell:
> > 
> > And we only have those for Mozilla-generated builds while the most
> > interesting build are the ones that get shipped widely, which are actually
> > built by partners.
> 
> This is true - do we have a bug tracking that?

I don't think so, and I also do not think that we'll get useful changesets from them, as they build against their own (non-public) repositories that often can contain proprietary changes.
Mentor: rhelmer
Whiteboard: [mentor=rhelmer@mozilla.com]
more trouble than it is worth
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.