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.
On Thu, Oct 21, 2021 at 1:47 PM 'jn...@cloudbees.com' via Jenkins Developers <jenkin...@googlegroups.com> 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.
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.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLX-wWQXYaX6RAR2DWXzU-_ABEHBNDF%3D7Tu8zNCbWYJKw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS53HetnKcjS%2BZWRanidi0wL5uDNvh%3De7gUyOu1gbFUb_A%40mail.gmail.com.
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.
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.
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLs27A9ODjSe537Ar3pRwkTYNiFr8WHX88Kd7EQtvUSow%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4prSBQsOx%3D2UmfqrjronEkn7j4qWWQvVk2WaGwS8ZPZA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicz862ZrAAx%2Bbjsb_E_6gTj8NkYk2x%3DNBZQvxNktLye3w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/97fdb78d-1275-4a4a-94c4-b1b9ce1b923an%40googlegroups.com.
I am open to extending irc-bot with a command like `jenkins-admin: invite user to the organisation` or `jenkins-admin: Make USER a member on TEAM` if that helps at all.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicz862ZrAAx%2Bbjsb_E_6gTj8NkYk2x%3DNBZQvxNktLye3w%40mail.gmail.com.