|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I don't see how this relates to the credentials plugin.
The credentials plugin adds screens for managing credentials external to Jenkins, e.g.
Jenkins » Manage Jenkins » Manage Credentials
which manages credentials available to all slaves and jobs (i.e. global scope) or all slaves (i.e. system scope)
and
People » (the currently logged in user) » Configure
Which has the option to store credentials for the currently logged in user.
The second one is only (to my knowledge) really effectively used by the CloudBees Deployer Plugin, but other plugins may start picking it up.