New issue
Advanced search Search tips

Issue 904578 link

Starred by 1 user

Issue metadata

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

Blocked on: View detail
issue 904573
issue 905751
issue 910630
issue 920429
issue 912340
issue 912345
issue 914909

Blocking:
issue 901883
issue 904572
issue 904581


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Move CIDB read operations to LUCI-equivalent concepts

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

Issue description

To transition to LUCI domain concepts and as a first step toward turning down CIDB, we should move all CBuildBot *read* operations to Buildbucket while maintaining CIDB writes for backward compatibility with other clients of CIDB.
 
Blocking: 904581
Labels: Disable-Nags
Components: Infra>Client>ChromeOS>CI
Blockedon: 905751
A recommendation.

We currently identify individual builds via a variety of keys. If we can standardize on buildbucket id, then a lot of the API changes become more straight forward.

CIDB can look up builds by that ID efficiently (there is a different look up function), and it obviously works in buildbucket APIs.
Sure, Don. I'll look into that. I'll schedule a 1-1 with you next week to discuss.

[I'm still getting to know buildbucket APIs.]
Blockedon: 910630
Blockedon: 912340
Blockedon: 912345
Blockedon: 914909
Blockedon: 920429

Sign in to add a comment