On Mon, Nov 25, 2019 at 2:03 PM James Nord <jn...@cloudbees.com> wrote: > IMO [installing plugins] should be another Permission
Just seems like permission bloat. I would expect `CONFIGURE` to imply the ability to install or update (but not downgrade) plugins from the UC. > for example if you have a curated locked down blessed update center you may > want to allow someone to install plugins from that without the ability to > configure jenkins (pipeline steps would be one example, of plugins that can > store their configuration at the folder level and do not need global config). While there are certainly plugins which do not require any global configuration, adding one sounds like configuring Jenkins to me. Why would an administrator wish to allow installation without configuration? > At the same time just because you can configure the system message does not > mean that you should be able to install new plugins. `CONFIGURE` means a lot more than setting the system message, I hope. And if you have this curated update center then what is the harm in letting a configurer install plugins from it? -- 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/CANfRfr2yc%2B8_ogpTCoHLs-zQ6JS5wrdLZ4Vtq-iArhmBunkhhw%40mail.gmail.com.
