Story
GitLab
Rio TintoRio Tinto Brings Build and Deploy onto GitLab
Rio Tinto, a materials organization in the United Kingdom, uses GitLab Security from GitLab to support continuous delivery for engineering teams.
Value results
| Category | Value result |
|---|---|
| Risk and compliance | Continuous delivery stays visible to adjacent teams through GitLab Security |
| 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
Inside Rio Tinto, continuous delivery used to depend on whoever still had the latest file. That pattern is common in materials groups working out of the United Kingdom. Engineering teams needed a system that would still make sense after the original project team moved on.
Rio Tinto 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 Rio Tinto 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.
