GitLab CI.
GitLab CI is the pipeline system built into GitLab, configured in a file alongside the code. It appears most often in organisations that chose GitLab for the whole toolchain — repository, review, CI, registry and issues in one product.
Where GitLab CI fits on a long engagement.
The integration is the argument. Review, pipeline, container registry and environments in one product removes the seams where tooling normally leaks, and for a self-hosted organisation it means one thing to operate rather than four.
Runners are where self-hosted GitLab estates struggle. Capacity, isolation and the difference between shared and dedicated runners decide both queue times and security posture, and they are usually configured once at adoption and never revisited as the organisation grows.
What an assigned team does with GitLab CI.
Self-hosted GitLab means runners are your problem, and runner capacity is set once at adoption and outgrown silently. Queue times climb, people stop waiting for pipelines, and the quality gate becomes advisory without anyone deciding it should.
Pipeline and platform are the same assignment here, given the product spans both. Where the constraint is the application rather than the toolchain, capacity moves toward software development outsourcing at the monthly cycle.
What we use GitLab CI for.
- Runner capacity and isolation Queue times reduced and build isolation established, rather than everything competing on one shared runner.
- Consistent pipelines across teams Templates and includes replacing per-project files that have drifted apart.
- Environments and review apps A running instance per merge request, so review happens against something real.
How GitLab CI capacity is assigned.
GitLab CI work is assigned under DevOps as a service, inside your own instance and your own runner infrastructure.
Tell us what your roadmap needs GitLab CI for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.