GitLab

I like that GitLab CI is easy to version and review because the pipeline is defined in a yaml file stored in the repo, so changes to the build and test workflow go through the same merge request process as production code. It's been great for standardizing how we run Playwright and Selenium suites, API tests, and contract checks for consistent container images, environment setup and predictable logs when something flakes. Test artifacts are also a big win for debugging in being able to publish test reports, screenshots, traces, and videos per job makes triage faster than digging through raw console output.

The built in features, especially automation in DevOps, SAST/DAST security protocols, and ease of scalability within our infrastructure.

I like the integrated CI/CD pipeline that makes automated builds and deployments easy, the comprehensive issue tracking and project management features, and the support for both cloud and on-premises deployment. It also has rich permissions and security scanning features that are strong and help in maintaining quality and compliance.

A single runner operation can become its own mini-platform where jobs get stuck, runner capacity planning is a pain, and keeping containers and dependencies stable across upgrades takes a lot of effort (especially once multiple teams pile onto the same fleet). Merge request pipelines are useful, but it's important to understand that they run against the source branch content (not the merged result by default), so there are times I still want merged-result testing to catch integration conflicts early. Also, caching and artifacts are easily misused at first, where cache is best for reusing dependencies, while artifacts are better for passing build outputs between stages and downloading reports later.

It is very complex to set up the service to begin with. The product is very complex and requires established system experience to be competent in. Costs can increase rapidly when expanding across infrastructure.

GitLab's interface can be sometimes be overwhelming for new users, the documentation sometimes lacks clarity, and some advanced features require a steep learning curve. Pricing for premium tiers can be high for smaller teams. Performance can degrade when handling very large repositories or pipelines.