Story
GitLab
Spin MasterSpin Master Uses GitLab Security for Build and Deploy
Spin Master, a consumer discretionary organization in Canada, uses GitLab Security from GitLab to support continuous delivery for engineering teams.
Value results
| Category | Value result |
|---|---|
| Productivity | Handoffs in continuous delivery sit in a shared queue instead of a mailbox trail |
| Risk and compliance | GitLab Security is the governed place engineering teams use for continuous delivery |
| Capability | New joiners can see how continuous delivery actually runs |
Story
Inside Spin Master, continuous delivery used to depend on whoever still had the latest file. That pattern is common in consumer discretionary groups working out of Canada. Engineering teams needed a system that would still make sense after the original project team moved on.
Spin Master uses GitLab Security from GitLab as the working layer for build and deploy. GitLab is a DevSecOps platform that combines source control, CI/CD, security scanning, and planning in one application. The practical change is simple: continuous delivery has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Spin Master gets from GitLab is a durable place to run continuous delivery and a way for engineering teams to see the same build and deploy at the same time.
