Building a CI/CD Process for Open Source Projects
summary
The talk explains how CI/CD for open-source projects differs from proprietary projects, focusing on challenges like many uncoordinated contributors, distributed time zones, and limited communication. It describes how these factors stretch the change-merge process and increase conflicts, and outlines how to design a CI/CD process that accounts for consortium-driven contributions and those collaboration issues.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 3:52Smart Device Link overview
- 6:03Consortium decisions
- 8:56Ford and Toyota versioning
- 12:31Testing tools
- 14:48RFC filtering problem
- 17:38Git conflict management
- 19:29Code sync open vs proprietary
- 21:58Commit history fixes
- 24:07Branch merging before release
- 25:55Code comments
- 27:00Multi-stage review
- 28:52Distributed team
- 31:46DevOps role
- 32:07CI/CD overview
- 35:25DevOps challenges
- 37:13Git branch structure
- 38:15Automated testing scope
- 39:40Jenkins integration
- 40:43Release management
- 41:50Docker standardization
- 44:26Jenkins scaling
- 45:51Summary & Q&A
related talks
07mWhat does open source need from CI/CD?
40mOpening Open-Source with DevOps
30mBringing Continuous Delivery to Open Source
48mStrong Foundations: Insightful learning vs trial-and-error in CI/CD
33mThe “C” in CI/CD is not for “Closed”
26mCI/CD in the OpenStack community and beyond
19mHow to utilize Open Source tools to create CI/CD & DevOps workflows
15mCI/CD: A History Lesson