Sounds good, could probably have one for the Jenkins core team too in RPU. On Thu, 21 Oct 2021 at 14:47, Baptiste Mathus <[email protected]> wrote:
> > > Le jeu. 21 oct. 2021 à 13:58, 'Daniel Beck' via Jenkins Developers < > [email protected]> a écrit : > >> >> >> On Thu, Oct 21, 2021 at 1:47 PM '[email protected]' via Jenkins >> Developers <[email protected]> wrote: >> >>> 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. >>> >> >> Sounds great. I would put the permissions declarations in RPU itself >> though, to make this just a layer of abstraction on top of the current >> definitions. >> > > Care to elaborate what you mean and how that would work? IIUC, what you're > describing would quite entail refactoring all existing "xyz-plugin > developer" groups on GitHub side? > And as you know we currently have close to no notion of github on RPU > side, like the names there are only artifactory's ones. > > >> >> Another use case, while RPU has purely artifact-based configuration >> (something I've wanted to change for a while but haven't found the time), >> would be multimodule projects deploying multiple artifacts. You don't need >> to be a company maintaining multiple plugins to have trouble with >> permissions. >> > > Do you mean we should improve RPU to better manage multi-modules? In that > case, I don't disagree, but I think we should put it in a separate bucket > so we can improve the situation iteratively. > I think what James describes can be done in a very quick way (still > clean), and what you describe here seems bigger. > > Still, I certainly agree it makes sense to define the full & final > "desired state" we want to be in. I _think_ this is what you're talking > about Daniel. > > -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLX-wWQXYaX6RAR2DWXzU-_ABEHBNDF%3D7Tu8zNCbWYJKw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLX-wWQXYaX6RAR2DWXzU-_ABEHBNDF%3D7Tu8zNCbWYJKw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS53HetnKcjS%2BZWRanidi0wL5uDNvh%3De7gUyOu1gbFUb_A%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS53HetnKcjS%2BZWRanidi0wL5uDNvh%3De7gUyOu1gbFUb_A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif4_3ryMaEnDOgH50jnvaUpUM%3DRyz7WYVm3B6yoOMhNMA%40mail.gmail.com.
