It's a matter how it is organized ...
If administrators only (a limited number of persons) have access to the 
manage section in Jenkins then it's probably a first step.
Also an option might be to use Vault.


On Monday, September 19, 2016 at 3:57:58 AM UTC+2, John Cho wrote:
>
> Hi,
> I am reading thru how to set up slaves on Jenkins using ssh keys.   Read 
> thru about three articles on how to do that.   According to them, the setup 
> is based upon using the slave as a ssh server with public and private keys 
> and it adds the slave's private key to the Jenkins master's credential 
> instead of the slave's public key.  Private key should never be shared.   
> Any thought on this practice?   Or, am I missing any?   Thanks in advance.
>
>

-- 
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/7b76bf38-986d-4d25-892c-97bb336a3e87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to