How we manage over1500 git repo’s CI/CD with a full InnerSource solution
summary
Managing CI/CD for over 1,500 Git repositories uses a reusable Jenkins pipeline framework plus stack implementations so each repo needs a two‑line Jenkinsfile instead of copy/pasting hundreds of lines; the central build team owns the framework while a community of practice (about half the contributions) maintains the Maven implementation, documentation is published to an internal wiki as part of the workflow CD, support runs through a Microsoft Teams channel, pipelines include security/static analysis/cloud deploy via Helm, and a migration to GitHub Actions is underway.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 1:55Company and tech scale
- 3:20CI/CD challenges with 17k repos
- 5:09InnerSource library solution
- 7:18Community of practice workflows
- 10:36Documentation and contributions
- 12:27Stability and future plans
related talks
29mFrom scheduled builds to commit triggered pipelines
33mScale your CI/CD setup for Cloud Native Microservices via InnerSource
36mAvoid Chaos in Our CI/CD Pipelines with Inner Source
47mCreating a CI/CD Pipeline for Your Shared Libraries
36mCI/CD BoF: Delivering Quality Quickly
36mUsing Jenkins to Build, Deploy, and Automate Projects
55mContinuous Integration on Steroids
30mImplementing Continuous Deployment with Jenkins & Gerritt