What is GitLab?

What it is

GitLab stores projects kept in Git. CI/CD pipelines test, build and deliver the software each time the code changes, and issues are tracked next to the code they refer to. The container registry holds the application images that Docker builds produce.

The self-managed edition runs on servers you control, which suits a business that wants its code and build systems in-house. It is most often compared with GitHub.

Why it matters to a business

• Group ownership: projects should live in a group the business owns, not under an employee's personal namespace. For a self-managed server, the business should also hold the administrator credentials.
• Tokens and deploy keys: these grant access just as user accounts do. Review accounts, tokens and keys on a schedule, and revoke the ones tied to anyone who leaves.
• Secrets in pipelines: passwords and API keys do not belong in repository files, because history preserves them. Use protected pipeline variables or a secrets manager.
• Backups you run yourself: a self-managed GitLab server needs its own backups and a tested restore. On a hosted service, still keep an independent copy of the code that matters most.

How KawaConnect works with GitLab

We host our own GitLab and use it every day. It runs our CI/CD pipelines and container image builds, holds our infrastructure as code, and drives GitOps delivery to Kubernetes.

On a client's GitLab we check that the business owns the top-level group, then go through accounts, tokens and deploy keys and remove any that belong to people who have left.

Learn more

• GitLab on WikipediaA neutral overview of what GitLab includes and how it is offered, helpful when comparing hosting options.
• GitLab websiteThe official site describing the platform.
• GitLab documentationOfficial guides covering pipelines, access control, and self-managed installs, written for administrators.