The Raiders of the Lost CICD and the quest for the Innersource Grail
summary
Demonstrates building a secured, maintainable CICD supply chain using Go, container images and GitLab CI components to replace long hardcoded YAML with versioned reusable jobs; shows migrating projects to component references and cutting pipeline clutter. Adds a centralized components catalog with docs, repo links, and automated usage tracking that reports which projects and versions rely on each component, enabling maintainers to spot outdated consumers. Claims this pipeline-first InnerSource approach scales, citing a 45% supply chain attack prediction to justify urgency.
AI-written summary · about
chapters (10)
- 0:00Introduction to the talk
- 1:11The lone rider’s CICD nightmare
- 3:24Building a basic CICD pipeline
- 5:13Discovering GitLab CI components
- 6:57Migrating to reusable components
- 8:21The need for an innerSource catalog
- 9:23Introducing the innerSource platform
- 11:31Why innerSource matters for CICD
- 12:15Strategies for successful innerSource
- 14:23Summary and Q&A
related talks
36mAvoid Chaos in Our CI/CD Pipelines with Inner Source
10mIt's Time We Start Securing Our CICD Pipelines
23mBuilding a Secure By-Design Pipeline with an Open-Source Stack
02h 47mPipes on Pipelines
48mStrong Foundations: Insightful learning vs trial-and-error in CI/CD
22mCI and CD as a Service: A multi-vendor driven system
33mScale your CI/CD setup for Cloud Native Microservices via InnerSource
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
