In this tutorial, I will show you how to establish an SSH connection from a Gitlab CI server to another server. It is not necessary for the other server to have the Gitlab CI runner installed. The ssh command includes the StrictHostKeyChecking flag. If this flag is set to no, the ssh client will automatically add host keys to the ~/.ssh/known_hosts file and will accept to connect to hosts whose host key has changed. This is why we create the .ssh folder and set the right permission to it. Resources: This is the .gitlab-ci.yml as seen in the video: https://gitlab.com/snippets/1952152 Using SSH keys with GitLab CI/CD - https://docs.gitlab.com/ee/ci/ssh_keys/ ssh-agent - https://www.ssh.com/ssh/agent ssh-add - https://www.ssh.com/ssh/add ___ // GitLab CI/CD ONLINE COURSE 👉 Want to learn more about CI/CD pipelines? Check my GitLab CI online course. Get it at a special price and help support this YouTube channel: http://www.vdespa.com/courses ___ // I HAVE A QUESTION! I do my best to answer all comments here on YouTube but I cannot make any guarantees. ___ // I HAVE A VIDEO IDEA Do you want me to create a video on a specific topic? Just fill out the form below: https://forms.gle/uWEzXFQ2viJtZtvZ7 ___ // P L A Y L I S T S ▸ Learn Gitlab CI |    • Gitlab   ___ // F R E E R E S O U R C E S ▸▸▸ Official Gitlab CI documentation https://docs.gitlab.com/ ▸▸▸ 👉 Subscribe to the "Testing and automation with Valentine" newsletter for bi-weekly tutorials, tips, and news from the industry. http://eepurl.com/gPwpU1 ___ // YOUR SUPPORT ON PATREON MATTERS If you enjoy this content, help me create more like this. Consider supporting me on Patreon. https://patreon.com/vdespa ___ // IMPRINT http://vdespa.com/imprint ---