GitLab CI

GitLab's continuous integration and delivery pipelines.

Cloud & DevOps

How we use GitLab CI

GitLab CI/CD is the automation built into GitLab. Pipelines defined in a single configuration file run tests, build containers and deploy applications whenever code changes, and GitLab can run them on its own servers or on runners you host.

How we use GitLab CI

  • Creating pipelines for testing, building and deploying web applications.
  • Using self-hosted runners for projects that must stay on private infrastructure.
  • Building and publishing Docker images to registries.
  • Setting up review apps so each feature branch can be tested live.

When GitLab CI is the right choice

GitLab CI is the right fit for teams that host their code on GitLab, including self-managed GitLab for privacy or compliance reasons. Its capabilities are comparable to GitHub Actions, so the choice usually follows where your repositories already are.

Related: Cloud & DevOps, CI/CD, GitHub Actions. Talk to our team about your project.

Frequently asked questions

Can GitLab CI run on our own servers?

Yes. GitLab runners can be installed on your infrastructure, so builds and code never leave your network if that is a requirement.

Can you move our pipelines from GitLab to GitHub?

Yes. Pipeline steps translate well between the two, and we migrate them along with repositories when you change platforms.

Can GitLab CI scan code for security issues?

Yes. GitLab offers security scanning for dependencies and code, and pipelines can run additional scanners to flag vulnerabilities before release.

Official GitLab CI website

Need a GitLab CI team?

Tell Softgarvik Technologies what you want to build. We reply within one working day with next steps and a free quote.