New issue
Advanced search Search tips

Issue 762012 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----


Previous locations:
gerrit:6825


Sign in to add a comment

[Regression] Non-committers can't CQ dry run their own CL

Project Member Reported by gab@chromium.org, Jul 24 2017

Issue description

Affected Version: Gerrit Code Review (2.14.1-2082-g4ea4c9831e)

What steps will reproduce the problem?
1. Have a non-committer request CQ dry-run on his CL

What is the expected output?
CQ dry run


What do you see instead?
Dry run: only full committers or CL owner with tryjob access are allowed to trigger CQ dry run

Example CL @ https://chromium-review.googlesource.com/c/563225

 

Comment 1 by logan@google.com, Sep 5 2017

Labels: -Type-Bug -Priority-3 Proj-Gerrit-Migration

Comment 2 by logan@google.com, Sep 5 2017

Project: chromium
Moved issue gerrit:6825 to now be  issue chromium:762012 .

Comment 3 by aga...@chromium.org, Sep 11 2017

Status: WontFix (was: New)
Yes, that's the whole point of "tryjob access" -- it's the permission you need in order to run tryjobs. We don't trust people to run arbitrary code in our test labs by default; if anyone could upload a change and then CQ+1 it without any committers looking at it, that would be a Bad Thing. This has been true for a long time, including on Rietveld.

Sign in to add a comment