Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Fwd: [cross-project-issues-dev] disable push to master for simrel


Everything should go through Gerrit *and* have a passing verification build.


Gunnar Wagenknecht

On Jun 26, 2018, at 13:04, Frederic Gurr <frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx> wrote:


I really like Jonah's idea (see below) to disable direct push access to
master for

Simrel releng engineer and maybe a few others should keep push
permissions to refs/heads/*.

Here is how the permissions for callisto-dev group would be changed:

# refs/for/refs/heads/*
 - Abandon
 - Create Reference
 - Forge Author Identity (inherited from All-Projects permissions)
 - Push  (inherited from All-Projects permissions)
 - Push Merge Commit  (inherited from All-Projects permissions)
 - Label Code-Review with range -2 to +2
 - Label Verified with range -1 to +1
 - Submit

# refs/heads/*
 - remove all permissions except:
   - Label Code-Review with range -2 to +2
   - Label Verified with range -1 to +1

I appreciate any pointers to missing/wrong Gerrit permissions.

Please vote for/against the proposal and/or give comments.



-------- Forwarded Message --------
Subject: [cross-project-issues-dev] disable push to master for simrel
Date: Mon, 25 Jun 2018 21:10:56 +0100
From: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

Hi folks,

Every release cycle there seems to be 1 or 2 (accidental) commits direct
to master bypassing gerrit & the validation step for the simrel. AFAIK
it is possible to disable direct push
in gerrit. Can this be done for the simrel?


Jonah Graham
Kichwa Coders Ltd. <>

Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH

Annastr. 44, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
<Attached Message Part.txt>_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top