New issue
Advanced search Search tips

Issue 904928 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 904881


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

BuildStart

Project Member Reported by cindyb@google.com, Nov 13

Issue description

Tell CIDB that build is starting
 
Status: Available (was: Untriaged)
Cc: jclinton@chromium.org
This also can go away, assuming we can use Buildbucket for CL Actions, which I think we agreed should work fine?
Eventually but we will have to write to CIDB for awhile while we wait for other teams who are reading from CIDB to migrate off. Dhanya has a plan for this that I just reviewed with him today so it might be good to chat with him about it.

Also, this stage does more than just write to CIDB: http://cs/chromeos_public/chromite/cbuildbot/stages/report_stages.py?l=237&rcl=cde48580e93da01999f0032e32ebf7fbca0e474e . It also writes metadata out so we need to evaluate who is using that and see if we can stop doing that.


Sign in to add a comment