How Lockheed Martin builds software faster, powered by DevSecOps
summary
Lockheed Martin standardizes on GitLab fronted by AWS to replace thousands of bespoke Jenkins servers, moving to containerized CI/CD pipelines and a reusable catalog server for versioned pipeline delivery into classified and sovereign environments. Adoption grows from 3k to 10k users and scales to roughly 250k builds per day. Success comes from a bottoms‑up rollout, three iterations of CI design (wizard → monolith → catalog), custody of security scans in CI, and automated, zero‑downtime upgrades.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:05Corporate Engineering
- 2:00What is Lockheed Martin
- 6:56Safety is the priority
- 9:30Transformation journey
- 10:18Shadow IT
- 18:48Successes
- 19:45GitLab
- 23:30Second Order Metrics
- 28:17Common CI Pipeline
- 33:56Security
- 37:48Sovereign cloud regions
- 38:43Are there potential efficiency gains
- 41:19Are there similarities with AI today
- 44:01Future proofing systems for AI
related talks
36mCI/CD BoF: Delivering Quality Quickly
21mDriving Cultural Change to Improve Software Development and CI/CD
29mScaling Across the Enterprise
46mThe Software Factory
30mJourney To The Cloud
54mFrom Code to Customer
22mKeynote: User Spotlight: Managing Cultural Transformation at Lockheed Martin
34mAmplifying CI/CD helped Wag! reduce release process by 600%