Last modified: 2014-11-20 00:29:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T75303, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73303 - Restrict 'integration' Gerrit group
Restrict 'integration' Gerrit group
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Chad H.
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-12 10:55 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-11-20 00:29 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2014-11-12 10:55:32 UTC
From a mail Timo sent me and I have missed:


Can we remove the inclusion of ldap/wmf group in 'integration'?

https://gerrit.wikimedia.org/r/#/admin/groups/10,members

In places where we want all of wmf to have access, we can manually include it as second group in permissions. For example, on https://gerrit.wikimedia.org/r/#/admin/projects/integration,access integration and ldap/wmf are both listed.

But for "Submit" I'd like to restrict e.g. integration/jenkins-job-builder-config to integration members. To avoid a mess like on https://gerrit.wikimedia.org/r/#/c/156193/

— Timo
Comment 1 Antoine "hashar" Musso (WMF) 2014-11-12 10:58:11 UTC
I agree integration/config.git submit right should only be granted to people having the ability to deploy Zuul configuration changes on the cluster.   Though we can also work on having the Zuul config deployed by the Jenkins job itself (scary).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links