New issue
Advanced search Search tips

Issue 903413 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 903409
issue 903414
issue 904269


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Implement SoM per-alert annotation capabilities

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

Issue description

CrOS currently uses Build Annotator <https://chromiumos-build-annotator.googleplex.com/build_annotations/builds_list/master-paladin/> to annotate every failed build. This is used for two business purposes: as input for when to automatically send kicked-out CL’s back in to the CQ and for historical failure analysis/reporting. This item tracks adding a similar annotation feature to SoM for which there would be an enum representing the failure reasons and a free-form text field for additional notes. In the case of a bad CL, an additional text field should appear allowing linking to that CL.

 
Blocking: 903414
Blocking: 904269
Labels: Disable-Nags
Labels: Milestone-CrOS

Sign in to add a comment