No the environment where Jenkins will be issuing the deploy. On Wed, Feb 3, 2016 at 4:26 AM, Michael Neale <[email protected]> wrote:
> By target env do you mean the slave/agent where the build runs? > > On Wednesday, February 3, 2016 at 1:25:29 AM UTC+11, MoBarger wrote: >> >> HI all, here is an odd question. Of course we can affect permissions of >> Jenkins jobs so that only defined people can run them. But has anyone ever >> locked down the target environments so that authenticated user in Jenkins >> is tested to see if they have rights to target env. Does that make sense? >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" 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-users/143879fe-ef94-4147-b3bd-fffe3e2bb0cc%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/143879fe-ef94-4147-b3bd-fffe3e2bb0cc%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/CAHz6asr2_NFpH-wRkuy_hz%2B4m0TJpdhvGEvRaAbxMS9o2FhjAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
