Story
GitLab
Eversource EnergyEversource Energy Uses GitLab Security for Build and Deploy
Eversource Energy, a utilities organization in the United States, uses GitLab Security from GitLab to support continuous delivery for engineering teams.
Shared GitLab Security workspaces help Eversource Energy keep continuous delivery honest across teams.
“Utilities work at Eversource Energy spans more than one site, even when headquarters sits in the United States.”
“Engineering teams asked for a shared way to run continuous delivery without freezing local judgment.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Risk and compliance | Continuous delivery stays visible to adjacent teams through GitLab Security |
| Risk and compliance | Engineering teams work from the same GitLab Security record for build and deploy |
| Capability | Named workflow replaces ad hoc routing for build and deploy |
Story
Utilities work at Eversource Energy spans more than one site, even when headquarters sits in the United States. Build and deploy was splitting across regional habits. Engineering teams asked for a shared way to run continuous delivery without freezing local judgment.
GitLab (GitLab Security) is what they standardized on. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. Eversource Energy uses it as the system of record for build and deploy, with engineering teams as the primary operators and other groups coming in through the same queue.
Leaders get a picture they can actually walk. Teams get fewer mystery statuses. The story is about operating change, not an unpublished percentage.
