While I don't know yet how it would work with our existing tooling, I am in 
favor of that approach and that would also be useful for other companies as 
well

On Thursday, 21 October 2021 at 13:47:24 UTC+2 jn...@cloudbees.com wrote:

> Hi all,
>
> CloudBees has a number of plugins in jenkins-ci organisation that we are 
> maintainers of.
>
> Currently when our internal teams change we need to modify multiple GitHub 
> repo settings and associated permissions RPU.  This is cumbersome (and 
> error prone) for us, and for the reviewers of the RPU PRs.
>
> I would like to propose (and ask for) a "CloudBees plugin developers" 
> group in the jenkinsci or that we can add CloudBees developers to and then 
> grant permissions to on the plugins that we maintain.  This will allow us 
> to just modify a single GitHub group and have the permissions updated in 
> all our plugins.
>
> Additionally to make RPU easier, we are planning to add support for groups 
> of users so that we would just need to modify a single "group definition 
> file" to update permissions in artifactory.
>
> This approach would then also be available to other companies with 
> multiple plugins in the Future.
>
> WDYT?
>
> /James
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2b63810e-2f5b-4a39-aea8-872419a6857en%40googlegroups.com.

Reply via email to