Auto-merge manifest/full.xml -> manifest-internal/external_full.xml |
||||||
Issue descriptionCurrently, when we update manifest/full.xml, it's also necessary to land a CL to update manifest-internal/external_full.xml (and vice-versa). This makes it extra awkward to make frequent manifest changes for things like pinned repositories. In addition, it means that anyone (like a partner) who can't submit to manifest-internal can't correctly submit manifest changes. It would be nice if the CQ somehow auto-managed this somehow, perhaps by auto-creating CLs that mirror changes from manifest/full.xml -> manifest-internal/external_full.xml. Any such logic needs to not break manifest testing in the CQ.
,
Mar 14 2016
@ aviv for prio
,
Mar 15 2016
Do we need/want partners making manifest changes? I like approach from comment #1. Would rather not build extra CL-creation tooling per initial post.
,
Mar 15 2016
The comment from #1 requires adding a new feature to the repo command, as well as an addition to the manifest file format.
,
Mar 28 2016
Triage notes: seems like high work, low reward. Marking as FixIt in case someone wants to pick it up.
,
Mar 28 2016
,
Apr 26 2016
,
Mar 10 2018
This bug has not been touched in over a year. It is probably no longer relevant. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dgarr...@chromium.org
, Mar 9 2016