New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 593393 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Auto-merge manifest/full.xml -> manifest-internal/external_full.xml

Project Member Reported by dgarr...@chromium.org, Mar 9 2016

Issue description

Currently, 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.
 
An alternative approach is to have repo directly import manifest/full.xml when checking out from manifest-internal.

Comment 2 by autumn@chromium.org, Mar 14 2016

Cc: akes...@chromium.org
@ aviv for prio
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.
The comment from #1 requires adding a new feature to the repo command, as well as an addition to the manifest file format.

Comment 5 by autumn@chromium.org, Mar 28 2016

Labels: -current-issue Hotlist-Fixit
Triage notes: seems like high work, low reward. Marking as FixIt in case someone wants to pick it up. 

Comment 6 by autumn@chromium.org, Mar 28 2016

Labels: -Pri-2 Pri-3

Comment 7 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
Status: Archived (was: Untriaged)
This bug has not been touched in over a year.  It is probably no longer relevant.

Sign in to add a comment