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

Issue 891691 link

Starred by 1 user
Status: Untriaged
Owner:
la...@chromium.org
Cc:
dgarr...@chromium.org
vapier@chromium.org
za...@chromium.org
█ bjanakiraman@chromium.org
█ puneetster@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Improve pre-built uprev process

Project Member Reported by shapiroc@chromium.org, Oct 3 
With the current instability in getting green runs on the master-paladin builder, we tend to go days->weeks before getting a green build, thus delaying the pre-built uprev process.

This has the side effect of slowing builds over time as the pre-builts age.

As part of the long term improvement efforts, we'd like re-evaluate this process and design/impl a more efficient process for uprevving the prebuilts.

Comment 1 by dgarr...@chromium.org, Oct 3 

For a while, I've been proposing a new set of builders that do nothing fetch TOT master, uprev ebuilds, compile, and upload prebuilts. No testing, alert on build failures. Possibly build Chrome prebuilts also.

Lann pointed out that if we start submitting CLs from the PreCQ (as we are wanting to do), then this is what the current CQ would become, especially if the PreCQ builders don't submit uprevs.

Comment 2 by dgarr...@chromium.org, Oct 3 

The original motivation was that it allows you to submit updates from multiple places without having to contend with ebuild uprev / prebuilt contention.

It's also nice in that it becomes a comprehensive check that TOT can compile, which is harder to guarantee after we start doing more complicated things in our submit processes (PFQs, CQ pipelining, chumping, PreCQ submissions, etc).
►

Sign in to add a comment