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

Issue 772484 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocking:
issue 680153



Sign in to add a comment

How can we avoid commit queue conflicts?

Project Member Reported by sjg@chromium.org, Oct 6 2017

Issue description

We have a problem with BSP ebuilds where different people want to add things and each has to rev the ebuild. With unified builds this is harder since there are many things in the same BSP shared across various models.

One option might be to use CROS_WORKON_SUBDIRS_TO_REV which was fixed recently in  crbug.com/764075 

 

Comment 1 by sjg@chromium.org, Oct 6 2017

Blocking: 680153

Comment 2 by sjg@chromium.org, Oct 6 2017

Labels: -Type-Bug Type-Feature
Owner: sjg@chromium.org
Status: Started (was: Untriaged)
Initial attempt here:

https://chrome-internal-review.googlesource.com/c/chromeos/overlays/overlay-coral-private/+/473472
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 15 2017

Comment 4 by sjg@chromium.org, Oct 17 2017

Summary: How can we avoid commit queue conflicts? (was: How can we avoid commit queue confflicts?)

Comment 5 by sjg@chromium.org, Oct 17 2017

This has been submitted, but we need to see at least once CL in coral BSP before we can be sure it works as intended.

Comment 6 by sjg@chromium.org, Nov 4 2017

Labels: Unibuild

Comment 7 by sjg@chromium.org, Nov 6 2017

Cc: yueherngl@chromium.org pbe...@chromium.org la...@chromium.org jclinton@chromium.org
Status: Fixed (was: Started)
This seems to work well. Closing this.

Sign in to add a comment