We have a Jenkins Job that builds something on node A and then needs to SCP it to node B. You can just put the SSH keys for node B on Node A, and SCP with an execute shell build step, however I suspect that keeping SSH keys on a Jenkins node is a bad practice, and would like to avoid it. What is the best practice regarding this use case? Is there a plugin or a feature for this? Should we just install Hashicorp Vault on the node and configure the keys there separately?

2 Answers 2


Yes, storing your ssh keys directly on a build node is a bad practice. Nodes can be replicated, deleted, or given access to from other systems, and you don't want to lose track of what systems have access to your secrets.

You should also not pass them directly into the build job, either as a parameter or as an environment variable. This can cause a huge headache with logging and tracking to make sure your keys aren't inadvertently output to places they shouldn't be. Instead, you should:

  1. Use a centralized secret store (such as Hashicorp Vault) to retrieve the secrets at build run-time.
  2. Use a plugin (such as the Credentials or SSH Credentials Plugin) to reference the keys during the build.
  • Do you have a link to an example or more in depth documentation of option 2? I couldn't find it and I've looked before asking this question.
    – Uberhumus
    Commented Aug 29, 2019 at 10:14
  • I've added the link to the relevant documentation for Jenkins declarative pipelines in the answer.
    – Preston Martin
    Commented Aug 29, 2019 at 20:07
  • Would be nice to mention in your answer that you used information that I contributed in my answer. :) @PrestonMartin
    – tnsh
    Commented Mar 20, 2023 at 14:43

I would suggest using the Jenkins Credentials Plugin.

Another method which is more useful in case the Jenkins nodes are not able to connect via SSH is by pushing it to some remote bucket from NodeA and using triggers or a webhook to pull it to NodeB. This might however require access to the internet.

To apply this use https://wiki.jenkins.io/display/JENKINS/SSH+Credentials+Plugin in conjunction with https://jenkins.io/doc/book/using/using-credentials.

  • Do you have a link to an example or more in depth documentation of the Jenkins Credentials Plugin? I couldn't find it and I've looked before asking this question.
    – Uberhumus
    Commented Aug 29, 2019 at 13:27
  • wiki.jenkins.io/display/JENKINS/SSH+Credentials+Plugin Use that in conjunction with jenkins.io/doc/book/using/using-credentials
    – tnsh
    Commented Sep 2, 2019 at 19:05
  • @TanishIslam If you are suggesting that NodeA push relevant files that NobeB requires to a bucket, then yes, using some remote file storage is an option. If you are suggesting that the keys for NodeA be pushed to a bucket and pulled by NodeB, I don't think that is a good suggestion. 1. Exposing your keys in an object store is just as bad if not worse than storing them on an instance. 2. The use case for what you would be using the object store for is exactly the scenario that a secret store is built for, except a secret store manages the secrets for you much more efficiently.
    – Preston Martin
    Commented Sep 3, 2019 at 21:04
  • @PrestonM pushing files was implied, and certainly not keys, because as clearly stated, if the nodes don't have SSH access, what keys could you possibly upload?
    – tnsh
    Commented Sep 5, 2019 at 5:11
  • The question states that the SSH keys for Node B would be stored on Node A. The nodes have SSH access.
    – Preston Martin
    Commented Sep 7, 2019 at 23:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.