Скачать или смотреть Deploying with GitLab CI: Why You Need SSH in Your Workflow

Learn why SSH is essential for deploying your applications using GitLab CI, even when using GitLab Runner on the same server.
---
This video is based on the question https://stackoverflow.com/q/66110367/ asked by the user 'Petr Schukin' ( https://stackoverflow.com/u/11023340/ ) and on the answer https://stackoverflow.com/a/66232293/ provided by the user 'Petr Schukin' ( https://stackoverflow.com/u/11023340/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: GitLab deploy to server without SSH

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Deploying with GitLab CI: Why You Need SSH in Your Workflow

As you embark on your journey into the world of GitLab CI (Continuous Integration), you might find yourself grappling with certain concepts, primary among them being the role of GitLab runners. One specific question that has come up is: Why do you need SSH for deployment when the GitLab runner is installed on the production server?

Let’s explore this question step by step, and clarify the significance of SSH in this workflow.

Understanding GitLab Runners

GitLab runners are essential for executing your CI/CD (Continuous Integration/Continuous Deployment) pipelines. Here’s what you need to know:

What is a GitLab Runner?

A GitLab runner is a lightweight agent that takes your code and executes the jobs defined in your .gitlab-ci.yml file.

Runner Types:

There are various types of runners that can be used, including:

Docker executor: Runs jobs in isolated Docker containers.

Shell executor: Executes jobs in the host’s shell environment.

The Role of SSH in Deployment

At first glance, it might seem redundant to deploy using SSH when the runner is on the same server. However, this approach has its rationale. Here’s why:

1. Isolation with Docker

When using a Docker executor, your jobs run in a container environment. This means:

Separation of Environments: The commands would run inside a container rather than directly on your server. Hence, not using SSH would mean that:

Your deployment commands wouldn't have access to the server's file system directly.

You could potentially deploy with a container-based environment that might not have the necessary permissions or dependencies.

2. Flexibility and Portability

Using SSH adds a layer of flexibility for future deployments:

Seamless Migration: Should you decide to migrate your application to a different server or set up another runner, you remain unaffected by the direct dependencies of the runner being the same as the deployment server.

Avoiding Constraints: If the shell executor is used, it might limit your pipeline to only deploy on the server running the runner, which creates a bottleneck and isn’t a scalable solution.

3. Best Practices

Incorporating SSH into your deployment strategy brings several best practices:

Security: It allows for secured connections to your production environment, reducing exposure of your server to unmanaged processes.

Control: You have enhanced control over when and how your deployments happen, leading to fewer chances for unintended changes or errors.

Conclusion

To summarize, while it may seem counterintuitive to use SSH for deploying to a server where the GitLab Runner is already installed, it serves important purposes:

Ensures that deployments are executed in the right environment.

Provides flexibility for future migrations.

Enhances security and control over your CI/CD process.

Next time you're setting up your deployment pipeline in GitLab CI, remember the vital role SSH plays in maintaining effective and scalable development environments. By understanding these components, you'll be better equipped to set up efficient workflows that grow alongside your project needs.