Continuous Delivery Foundation hopes to bring rhyme and reason to CI/CD
At the Open Source Leadership Summit (OSLS), the Linux Foundation introduced, with a host of partners, the Continuous Delivery Foundation (CDF). Its goal? The not-so-modest one of bringing sense to continuous integration and continuous delivery (CI/CD). Everyone who's invested in DevOps, loves CI/CD. CI gives you a consistent and automated way to build, package, and test applications. CD then picks up the ball by automating the delivery of applications. What's not to love? As Christy Wilson. a Google software engineer, explained in a OSLS keynote:Everybody needs CI/CD. Before you can try to apply fancy modern development practices like chaos engineering, or progressive delivery, the idea of start with CI/CD. If you want your projects to scale, if you want to sustain growth, if you want to grow your open-source, contributor base, you have to know CI/CD. Regardless of the size of your company, whether you have thousands of engineers; when you're a startup; whether you're working on greenfield or you're maintaining legacy software, you have to have a CI/CD. That's all well and good, but it leaves the questions: "Which CI/CD?" As one executive at OSLS put it, "I can't keep up with them and I do this for a living!"Currently, the CI/CD tool ecosystem is extremely fragmented. This leaves CI/CD developers needing guidance on best practices and how to secure their software supply chains. That's where CDF comes in. Or, as Kohsuke Kawaguchi, Jenkins CI/CD project founder and CloudBees' CTO, put it, "CDF will remove barriers between CI/CD projects.