New issue
Advanced search Search tips

Issue 865224 link

Starred by 0 users
Status: WontFix
Owner:
liaoyuke@chromium.org
Closed: Jan 8
Cc:
chanli@chromium.org
seanmccullough@chromium.org
liaoyuke@chromium.org
st...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

chromium-try-flakes should have regular deployments

Project Member Reported by agable@google.com, Jul 18 
Today I was paged[1] because monorail was updated to a version which broke chromium-try-flakes' use of one of its APIs. However, the code necessary for chromium-try-flakes to use the API was live for 15 days before the switch was made.

If chromium-try-flakes deployed on a regular weekly cadence, this issue would have been avoided.

Comment 1 by st...@chromium.org, Aug 8

Owner: liaoyuke@chromium.org
Status: Assigned (was: Untriaged)
Many thanks for the feedback!

Usually, we don't deploy CTF if there is no change within itself or the underlying dependencies that are required for it. The code change on Monorail client is intended for the new flake detection in Findit instead of CTF.

Since CTF will be replaced by the new flake detection soon, we might not introduce a change to deployment process to it. (Findit is deployed in a weekly basis, so it won't be a problem for the new flake detection)

Assign to Yuke as he works on the new flake detection.

Comment 2 by liaoyuke@chromium.org, Jan 8

Status: WontFix (was: Assigned)
try-flakes is deprecated.
►

Sign in to add a comment