New issue
Advanced search Search tips

Issue 901883 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Feature


Sign in to add a comment

Embrace LUCI domain model in CBuildBot/Recipe utilization of LUCI

Project Member Reported by jclinton@chromium.org, Nov 5

Issue description

This is a master tracking bug for implementing full utilization of the LUCI domain model within CBuildbot.

So far, that seems to include:
* Move to use LUCI 'builders', one for each builder config, instead of the 3 builders that we have now (Prod, PreCQ, TryJob)

* Move to use 'buildset' tag to index builds in the same parent/child group. Also consider using newly proposed buildbucket.v2.Build.parent_id field for tracking parent/child relationships.

* Export gitiles commit metadata from all builds in a parent/child relationship such that Milo knows how to group these builds together. This will be the commit of the manifest repo from which the parent and child builds all start to build (before cherry-picking).

* Embrance 'category' fields in
https://chromium.googlesource.com/chromium/src/+/master/infra/config/global/luci-milo.cfg#318

* Export Milo blamelist metadata such that all CL's in a build are renderable by Milo (such as what Chrome has today in Milo). I'm not sure what this entails.


 
Labels: CrOSParallelCQ
Also:

* Export Buildbucket buckets where there is one bucket per project. This will later be used for ACL boundaries.

Blocking: 903364
Blockedon: 903365
Labels: -Pri-1 Pri-0
Blockedon: 903370
Blockedon: 903371
Blockedon: 903372
Blockedon: 903375
Blockedon: 903367
Blockedon: 903376
Blocking: 904274
Blocking: 904572
Blockedon: 904578
Labels: Disable-Nags

Sign in to add a comment