Closed
Bug 625178
Opened 15 years ago
Closed 11 years ago
buildapi should show which changes have gone through our systems
Categories
(Release Engineering :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: armenzg, Unassigned)
Details
(Keywords: buildapi)
I would like to see in a page every change that we pick up.
date - HH:MM mozilla-central/9217634f7b9e
date - HH:MM mobile-browser/1234534f7b9e
date - HH:MM l10n-central/ABCDE34f7b9e
Each one of them should have a link to their list of jobs associated to that changeset. Pretty much to send us to the currently existing page we have in buildapi:
> build.m.o/buildapi/revision/try/9eef3607035d
Comment 1•15 years ago
|
||
Might be slightly complicated to get the data from the db for this. ie you can use the sourcestamps table but need to exclude 'branches' which are *talos and *unittest (from sendchanges), and deal with duplicated sourcestamps for any revision (more than one poller for branches that trigger mobile builds). Then you can join back to changes (via sourcestamp_changes) to get changes.whentimestamp. IIRC that's the timestamp in hg rather than when we picked it up.
To make this really useful you probably want some sort of green/orange/red/purple counts for each revision. Would add lots more querying and would impact page load time. anamarias knows about this stuff.
Priority: -- → P5
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 2•11 years ago
|
||
This sounds like TBPL or treeherder.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•