Home Cd software 5 more CI / CD misconceptions, explained

5 more CI / CD misconceptions, explained



A successful DevOps transformation requires effective and efficient continuous integration and continuous delivery / deployment (CI / CD) pipeline. One step towards establishing an effective CI / CD is to eliminate common misconceptions that can delay progress or cause labor. Part 1 of this two-part series presented the main misconceptions about CI / CD from the perspective of DevOps Institute Ambassadors. The second part continues to explore these misperceptions.

Any organization moving towards DevOps maturity should consider whether it is being misled by some of these common assumptions. A misconception that I run into frequently is the idea that CI / CD is a potential replacement for the need for skilled humans. However, the goal of CI / CD automation is to perform consistent and redundant tasks so that humans can be free to perform work that requires unique skills and critical thinking.

[ How can DevOps accelerate your digital transformation initiative? Read also: Digital transformation: 10 more ways DevOps can help. ]

Here are some more misconceptions, shared by DevOps Institute Ambassadors:

False idea: There is no heavy weight

“Most people think CI / CD tools completely automate the application lifecycle process. Not true. Some CI / CD engines only orchestrate. You create integrations with the rest of the ecosystem to do the heavy lifting of the automated testing, configuration management, and deployments that are the heart of the process. In other words, it takes a village. -Tracy Ragan, CEO and co-founder of Deploy Hub

False idea: Customers don’t want to change so often

“Continuous delivery isn’t about constantly delivering new functionality. The CD has two main purposes: First, the CD is about operations. When things go wrong in the middle of the night, your customers want to change that quickly. We need the ability to quickly and safely repair production while we are tired and stressed at 3 a.m. because our standard delivery process takes several hours or days to complete. We continually check our patch process using the patch process to deliver new changes on a daily basis. In a CD workflow, every change is an emergency change and emergency changes use our tested best quality process.

“Second, CD is about discovering and removing delivery constraints and labor. Development should be about delivering the right thing, not wasting time How? ‘Or’ What to get this change. By using the CD as a tool to eliminate unnecessary verification and automate verification, compliance, and security, we can relentlessly remove drag from the development process to reduce drag from idea to delivery. -Bryan Finster, Distinguished Software Engineer, DoD Platform One

[ Join SKILup Day: CI/CD from DevOps Institute on July 22. Register here. ]

False idea: Every construction leads to production

“People think that if they build via CI / CD, every build is deployed to production. This is not true. CI / CD isn’t just the process of pushing code into production – it gives developers the ability to control what code can go into production, what code can be tested, and what is really needed to go into production. A CI / CD pipeline is only production ready if it has gone through all the safety and quality processes to be truly ready for deployment. -Vishnu Vasudevan, Head of Engineering and Product Development, Opsera

False idea: CI / CD is DevOps

“People assume that implementing CI / CD tools means your organization is practicing DevOps. This is often not the case because there are mindsets, processes, people and skills that also need to change. -Jamal Walsh, Technical Product Manager, The group itself

False idea: CI / CD makes deployment transparent

“CI / CD in business means the code is deployed like magic. Under the hood, several jobs must be done and currently, several challenges prevent this wish from being realized. Put simply, the company sees it as an end-to-end (developers) to end-to-end (deployment) pipeline, but there are several leaks, which makes deployments non-transparent. -Sharath Dodda, Head of IT Design and Development, TD Bank

[ How can automation free up more staff time for innovation? Get the free eBook: Managing IT with Automation. ]



Please enter your comment!
Please enter your name here