Thanks Catlee, this should indeed be a huge help to sheriffs.
How does the new mechanism interact with gaia.json, if it does?
Will builds other than b2g desktop now utilize gaia.json as well?
Jonathan
On 1/17/2014 7:58 AM, Chris AtLee
wrote:
Hi,
Yesterday we switched how B2G device builds on the trunk trees [1]
get built.
We are keeping copies of each device's manifest up-to-date in the
tree will the revisions for each project fully specified. e.g.
https://hg.mozilla.org/integration/b2g-inbound/file/fa8e7793c44b/b2g/config/mako/sources.xml
In the background, we have tools running that checkout the
b2g-manifests repo, and then for each device load the official
upstream manifest, follow all the includes, and resolve all
revision references in the manifest to absolute commit ids, and
then land those into gecko.
This will be a big help to sheriffs, as it pins down the revisions
of various b2g repositories used for each gecko change.
Please let me know if you see any problems with the builds as a
result of this change. Work is being tracked in bug 899969 [2].
Thanks!
Chris
[1] b2g-inbound, mozilla-central, mozilla-inbound, etc.
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=899969
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
|
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
