On Thu, Sep 19, 2019 at 4:21 AM Jhonny Oliveira <jhonny.olive...@gmail.com> wrote:
> Hi! > > is it possible to limit the usage of a credential to a specific slave? > Not with Jenkins as far as I know. Credentials can be defined on the Jenkins master, on folders, and on multibranch Pipelines. They can't be defined on Freestyle jobs or on agents. > With this restriction, I could fully empower developers to create their > own Pipelines (Jenkinsfile) while avoiding passwords to be leaked in the > wrong slaves/environments. > Could you attach the credentials to a folder and then limit access to the folders instead? Those with access to the folder can use the credential attached to that folder. Those without access to the folder could not use that credential. > > Just for further context, in my scenario and at infrastructure level, only > specific slaves are allowed to deploy to specific environments. E.g.: > dev_slave -> deploy to DEV; tst_slave -> deploy to TST and so on. > > Cheers, > Jhonny Oliveira > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/2540cf8f-0413-4ec1-ae4a-136f2eeaf894%40googlegroups.com > . > -- Thanks! Mark Waite -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFCvn4k-DW%2BY5ew30bLAhaNBc-UHgaFx6dDTn17qAoyRQ%40mail.gmail.com.
