At EclipseCon Europe 2019 I attended a very interesting talk entitled "CI systems need care, too! Here's how we improved ours over the years". It was an eye opener! Here's what I gathered.
- New developer comes to a Company
- Company sells a software product built by a CI system
- The CI system is a cobbled hack
- Developer raises awareness that
- CI is important
- Fast CI feedback loop is important
- CI is on the criticali path to profit (delivering the product)
- Developer becomes an IT sysadmin and a Release Engineer to fix the CI, thus distracted from the actual task of improving the product.
The Eclipse CBI project (Common Build Infra) has been solving these problems for over 12 years. If you can relate to the unfortunate scenario above, here's what I can suggest:
- Host your code at the Eclipse Foundation.
- With IT and Release Engineers on staff, you can focus on code, not the build.
- With Best Practices, we can help with your build so you can focus on code.
- If you must fix your CI system yourself:
We've all been guilty of reinventing the wheel. Let's not do that. We're here to help (slides to come).