New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 770396 link

Starred by 1 user
Status: WontFix
Owner:
█ robert...@chromium.org
Last visit > 30 days ago
Closed: Jan 2018
Cc:
no...@chromium.org
st...@chromium.org
█ robert...@chromium.org
chanli@chromium.org
lijeffrey@chromium.org
liaoyuke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[cr-audit-commits] Do not use .sourceStamp.changes to ensure that a build contains a revision.

Project Member Reported by robert...@chromium.org, Sep 29 2017 
Instead, get the build's revision and the previous build's revision, and then get a log between the two from gitiles.

This affects the CulpritInBuildRule.

Comment 1 by robert...@chromium.org, Sep 29 2017

Cc: st...@chromium.org
nodir@, could you comment on the expected timeline for the deprecation of .sourcestamp.changes?

Comment 2 by no...@chromium.org, Oct 1 2017 

We’ve discovered that gatekeeper also needs sourceStamp and blamelist so emulated responses will include those.

Comment 3 by robert...@chromium.org, Jan 5 2018

Status: WontFix (was: Untriaged)
►

Sign in to add a comment