With Docker and k8's, this is not your grandparents' infra anymore!
summary
Eclipse infrastructure migrates roughly 180–200 Jenkins instance per project setups onto Kubernetes/OpenShift, replacing a dozen aging servers with an eight-node compute cluster (and plans to grow) so builds scale without single jobs hogging 256GB machines. CI/CD runs Jenkins masters plus external agents, nginx provides front-end caching for downloads and wiki, OpenID Connect for auth, api.eclipse.org centralizes REST access, and a privacy policy for Google Analytics and GDPR compliance is being formalized.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:39The List of Services That We Provide to the Community
- 2:17What Did Your Grandparents Used To Do for Code
- 4:09Jenkins
- 5:38A Jenkins Instance per Project
- 8:44What Jenkins Looks like
- 15:00Open Id Connect
- 15:22Data Privacy
- 17:04The Eclipse Hosted Services Privacy and Acceptable Usage Policy
- 18:24Gdpr
- 19:26Quicksilver Theme
related talks
35mJenkins Scaling and Organization for an Efficient CI
34mContinuously building impressive software - How can we keep the build green?
13mEvolution of containers in continuous integration
05mJenkins in the Cloud
38mUsing Containers for Continuous Integration and Continuous Delivery [I]
27mContinuous Integration at Scale on Kubernetes [B]
41mScaling Jenkins
43mUsing containers for Continuous Integration Delivery