The SSH Agent build feature runs an SSH agent with the selected uploaded SSH key during a build. When your build script runs an SSH client, it uses the SSH agent with the loaded key.
Check SSH Keys Management for SSH key upload notes.
The TeamCity SSH agent uses a native SSH agent from the OpenSSH included with Linux and macOS, so the feature works out of the box for these OSs. For Windows, OpenSSH needs to be installed (for example, as a part of CygWin, MinGW or a part of Git distribution for Windows).
The SSH agent must be added to
$PATH on Unix-like OSs and to
%PATH% on Windows.
For each TeamCity build agent, a separate SSH agent is started, so it is possible to use this feature if several build agents are installed on the same machine.
Disabling SSH Host Key Checking
The first time you connect to a remote host, the SSH client asks if you want to add a remote host's fingerprint to the known hosts database at
To avoid such prompts during a build, you need to configure the known hosts database beforehand. If you trust the hosts you are connecting to, you can disable known hosts checks:
either for all connections by adding something like this in
~/.ssh/config:Host * StrictHostKeyChecking no
or for an individual command by running an SSH client with the
-o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=nooptions.
See more information in the man pages for
Using Multiple Keys in One Build
If a build needs to authenticate in several external systems, it can use more than one SSH key.
To use multiple SSH keys in a build:
On the project level: add the keys on the SSH Keys page.
On the build configuration level: add multiple SSH Agent build features, one per each key.
When a build starts, it downloads the SSH keys from the server and runs an SSH agent that distributes the keys on demand of other build steps.