Story
GitLab
CignaCigna Modernizes Build and Deploy with GitLab
Cigna, a health care organization in the United States, uses GitLab CI/CD from GitLab to support continuous delivery for engineering teams.
Cigna uses GitLab CI/CD to build, test, and ship from one pipeline instead of a pile of scripts.
“Cigna is based in the United States and runs health care operations at a scale where build and deploy cannot live in side channels.”
“Engineering teams were reconciling competing copies of the same work, which slowed continuous delivery and hid who owned the next step.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Engineering teams work from the same GitLab CI/CD record for build and deploy |
| Capability | Build and deploy can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for build and deploy |
Story
Cigna is based in the United States and runs health care operations at a scale where build and deploy cannot live in side channels. Engineering teams were reconciling competing copies of the same work, which slowed continuous delivery and hid who owned the next step.
The company runs continuous delivery on GitLab, with GitLab CI/CD as the product engineering teams actually open. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. For Cigna, that means engineering teams can open one workflow, see build and deploy, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for build and deploy.
