Goldeneye changes for unified builds |
||||||
Issue descriptionAdd support for unified builds to Goldeneye.
,
Jan 19 2017
Update: I spoke to Christine today and the plan is:
- Update metadata.json file to contain unified build info
- Agree on entity structure
E.g. board has a one to many relationship with model
- Use 'sub-board' instead of model (eek!)
- When we ingest metadata, need to deal with info which needs to be at the model rather than the board level
,
Jan 23 2017
Some simple metadata changes proposed here: https://docs.google.com/document/d/1XG8motvGyn-yevrzkskhUuhynWi3o86VjrlGs9p94fw/edit#bookmark=id.v9h9xeom4aif
,
Jan 23 2017
,
Feb 13 2017
,
Mar 16 2017
OK I am going to get back into this now that firmware update, recovery mode, etc. are looking good.
,
Apr 7 2017
GoldenEye-specific doc describing changes is here: go/cros-unified-builds-goldeneye
,
May 1 2017
Update: Split into three bugs in buganizer since this is google3 work: b/36516649 GoldenEye back-end changes for unified builds b/37678282 GoldenEye UI changes for unified builds v/37744352 Implement back end changes for pushing a unified-build update
,
May 1 2017
,
Sep 1 2017
,
Nov 4 2017
,
Jan 2 2018
This is complete for v1. We can track future work in other bugs. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sjg@chromium.org
, Jan 12 2017