From the Enterprisers Project: 6 CI/CD Pitfalls to avoid
January 14, 2019 | by
One of the great benefits of building out your container native infrastructure is enabling continuous integration and continuous deployment. As teams struggle to push out more features faster, having a reliable, quick-provisioned environment for build and test activities is table stakes. You cannot perform 20 builds in an eight hour work day if each build takes two hours. More builds mean more tests, more features and more progress. While container native infrastructure enables this process, CI/CD comes with its own challenges, even when the needed infrastructure is in place. Continuous integration and continuous deployment are where rubber meets road on the trek towards the digital transformation.
The Enterprisers Project wrote up a useful list of 6 pitfalls to avoid in your CI/CD journey. These are real world pitfalls, that should be helpful for your overall team. Rather unlike the pitfall we stumbled across at the bottom of the page in this old Linux Kernel module programming guide. Instead, Kevin Casey has assembled some good advice for teams trying to increase velocity., such as this snippet from number 3:
Don't give people a way to bypass the CI/CD pipeline
Don’t enable team members to bypass the pipeline other than under the most extraordinary of circumstances. This can be particularly important if you’re dealing with skepticism or cultural stasis in the earlier stages of your shift to CI/CD.
“If your CI/CD platform is not the only way, excluding an emergency break-glass method, to deploy code to your production environment, it will become tempting for teams to work around it when your testing [finds] code issues that are not easily solvable,” says Jerry Gamblin, principal security engineer at Kenna Security.
Introduction The Node Tuning Operator (NTO) is a Second Level Operator (SLO) that ships with OpenShift Container Platform (OCP) 4 by default. It has come a long way since its first release, and this ...