Based on the executor used you might find harder or easier to debug problems, cache, persist and share build assets and dependencies and scale / utilize your compute. These executors allow running your runners with additional features like private container registry, interactive web terminal, cache, artifacts, etc. GitLab runners have the concept of executors, currently supported executors are: Luckily GitLab allows using self-hosted gitlab runners! You can run a single Go binary on a variety of OSes. Processing sensitive data might be a no-go for a lot of corporations. You could always buy extra minutes but if you run a lot of pipelines, things might get expensive.Īnother reason not to use shared runners can be security concerns. Shared runners can be very slow and you are limited to “CI pipeline minutes” per month based on your paid plan. I will show how to run GitLab runner on AWS using terraform, Elastic Kubernetes Service and GitLab kubernetes integration. Though you might want to run your own runner in your private or public cloud. Hosted solution offers shared runners and some usage minutes based on your paid plan (even if the free tier).
GitLab-CI/CD is a great and powerful product for CI/CD pipelines.
0 kommentar(er)
