I appreciate the warnings but this is a plugin used internally by our company for release automation. Context always help :)
On Tuesday, October 24, 2017 at 3:12:50 PM UTC-5, Shaun Thompson wrote: > > That doesn't line up with what I'm seeing. Plugin fails to create the job > so an ACL is in effect. I guess I'll figure it out on my own. > > On Tuesday, October 24, 2017 at 1:11:08 PM UTC-5, Jesse Glick wrote: >> >> On Tue, Oct 24, 2017 at 1:23 PM, Shaun Thompson <sth...@gmail.com> >> wrote: >> > By logged in user, I'm referring to the user that initiated the plugin >> > installation. >> >> There is no information available to that effect, if such a concept >> were even reliably meaningful, which it is not. >> >> Clearly anyone able to install a plugin can do whatever they like—they >> must be an administrator. So if your plugin wishes to create a job >> during installation (again, a bad idea as a rule), just do so. You >> should be running as `SYSTEM`, which can do anything. >> > -- 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/5d74db7f-cb93-4748-8efb-8df061f58516%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
