New issue
Advanced search Search tips

Issue 705777 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

cbuildbot_launch always does an internal checkout, which is wasteful for external builds.

Project Member Reported by dgarr...@chromium.org, Mar 28 2017

Issue description

cbuildbot_launch always does an internal checkout before launching cbuildbot, but if the build config to be launched is external, this is wasteful (though cbuildbot should do the right thing).

It's not possible for cbuildbot_launch to examine build configs, and so it can't tell if the build is internal or external from the config name.

However, the chromite recipe does know, and we might be able to take advantage of this somehow.

PS: This does not prevent correct builds, just wastes time/bandwidth/disk io at the beginning of each build.
 

Comment 1 by aut...@google.com, Mar 28 2017

Labels: -current-issue
Labels: -Pri-2 Pri-3
Status: Assigned (was: Untriaged)
This appears to be a 10-30 second difference.
Status: Available (was: Assigned)
In production, the performance difference is a bit higher.
Components: Infra>Client>ChromeOS>CI
Components: -Infra>Client>ChromeOS
Status: Untriaged (was: Available)
Status: Un (was: Untriaged)
Owner: ----
Status: Untriaged (was: Un)

Sign in to add a comment