![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
windows-slaves-plugin |
|
Created:
|
25/Nov/14 8:54 PM
|
|
Description:
|
When connecting Unix machines through SSH,the SSH Slaves plugin uses the SSH Credentials plugin to be able to store the SSH credentials in one place. Then when or if these credentials change, they only have to be updated in one place to update every affected SSH slave connected.
However, when adding a Windows slave, using the "Let Jenkins Control this Windows Slave as Windows service" method, each slave connected has its own authentication credentials. This means after a password change that every Windows slave configuration must be updated. These credentials for Windows slaves should be stored in the Credentials Manager plugin, and used from there, then the storing of credentials for Windows or Unix slaves would be consistent, and the maintenance of Windows slaves would be reduced.
|
|
Environment:
|
jenkins 1.576, windows-slaves-plugin 1.0
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Rick Patterson
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
