Continuously building impressive software - How can we keep the build green?
summary
The Eclipse Foundation runs a Common Build Infrastructure serving 429 Eclipse projects with a cluster of 250 Jenkins controllers, 500+ CPU cores, 2.5 TB RAM and 24 TB disk, running >1,000 pods; builds use dynamic and static agents (Linux, Windows, macOS) and GitHub Actions/GitLab Runners. Recommendations include migrating off Gerrit, move wikis and issues to GitHub/GitLab, use Jenkins Pipelines, avoid concurrent jobs, prefer webhooks over polling, and a signing service is planned as accessible to Eclipse projects.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:50Eclipse build infrastructure
- 8:17Common issues and support
- 11:09Reliable build best practices
- 13:39Legacy system migrations
- 18:11Security and supply chain
- 21:20Future automation plans
- 23:08Q&A
related talks
28mWith Docker and k8's, this is not your grandparents' infra anymore!
27mNext generation CI - building Eclipse projects on the new CBI build farm
35mJenkins Scaling and Organization for an Efficient CI
34mHelping Enterprises Scale Their Jenkins Software Practices and Tools
42mJenkins: Enabling Agility and Efficiency
27mAutomation, Innovation and Continuous Delivery
55mContinuous Integration on Steroids
46mThe Software Factory