Closed
Bug 884904
Opened 11 years ago
Closed 8 years ago
Make gaia-central corresponding git commit discoverable from b2g/config/gaia.json
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nbp, Unassigned)
References
Details
Currently b2g/config/gaia.json contains a reference to a mercurial changeset. This changeset depends on the conversion made by hg-git which stores the mapping between changeset and commits into a map-file. Ideally, we should modify the "Gaia Pushbot <release+gaiajson@mozilla.com>", such as it also add a reference to the sha1 in addition to the changeset. An other solution would be to make the mapfile accessible to everybody through a ftp/http server. This is not ideal as this would require people to do some network access to clone the full map-file.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 2•11 years ago
|
||
Is there any ETA on this being available?
Updated•10 years ago
|
Summary: Make gaia-central corresponding commit discoverable from b2g/config/gaia.json → Make gaia-central corresponding git commit discoverable from b2g/config/gaia.json
Comment 3•8 years ago
|
||
This was fixed a while ago.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•