New issue
Advanced search Search tips

Issue 696614 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----


Previous locations:
gerrit:5656


Sign in to add a comment

Add ability to cancel CQ run

Project Member Reported by drott@chromium.org, Feb 27 2017

Issue description

Affected Version: 2.13.5-2896-gc200c14eec
Example CL, Chromium: https://chromium-review.googlesource.com/c/444189/

What steps will reproduce the problem?
1. Click on "CQ"
2. Observe "CQ running..." as button label
3. Look for ability to cancel CQ submit

What is the expected output?
It should be possible to cancel the CQ run.

What do you see instead?
I don't find an option to do that.




Please provide any additional information below.

 

Comment 1 by logan@google.com, Feb 27 2017

Components: -PolyGerrit
Labels: Proj-Gerrit-Migration

Comment 2 by logan@google.com, Feb 27 2017

Project: chromium
Moved issue gerrit:5656 to now be  issue chromium:696614 .
Components: Infra>CQ
Labels: -Proj-Gerrit-Migration
Status: Available (was: New)
Unfortunately the CQ doesn't have the ability to cancel full runs at all, so there's no reasonable way for Gerrit to provide that functionality either. Moving into CQ component.
Components: -Infra>CQ Infra>Codereview>Gerrit
Labels: Proj-Gerrit-Migration
Status: Untriaged (was: Available)
agable@ this is not correct, adding back to Gerrit tracker.

FTR, CQ has ability to cancel both Dry and Full runs:
 * In Rietveld, it means unchecking the commit checkbox.
 * In Gerrit, there are several ways:
    * best is remove your vote on CQ+1 (or CQ+2) which triggered CQ. 
      A button "cancel CQ" can be added to Gerrit UI to do exactly this.
    * also works is editing description or uploading a new patchset :)

However, even though CQ run is aborted, any tryjobs started will continue to run.
Labels: Milestone-Launch
Owner: aga...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to agable to include on FAQ

Comment 6 by aga...@chromium.org, Apr 20 2017

Status: Fixed (was: Assigned)
FAQ updated.

Sign in to add a comment