Limiting Repo Access

[Justin Collins]

Hi all, and apologies if this has come up before.

On GitHub, the JenkinsCI organization has a ton of "teams" - on per plugin plus some others. I am not sure what the process is at the moment, but the team I'm on (jenkinsci/brakeman-plugin-developers) is often granted access to other plugin repos I have nothing to do with. I don't want this access. I don't want to be able to perform dangerous operations (e.g. deleting the repo) on random repos. In the past I've actually gone through and removed the brakeman-plugin-developers team from other repos, but I don't seem to have this ability now.

If there is going to be one team set up per repo/plugin, then the team should be restricted to that repo. Right now ~150 teams have access to jenkinsci/brakeman-plugin. That kind of defeats the point of having teams.

Thanks,

Justin

[Kohsuke Kawaguchi]

If I recall correctly, when a new repository is added to an
organization, somehow that repo gets added to all the teams. And while
our IRC bot does try to fix this up, if it fails in the middle, it
leaves the mess behind.

I think what I'm going to do is to write a program that periodically
runs and inspect all the team setup and do the fix up.

> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-de...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>


--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins