CI/CD Challenges Are Real
(and Plentiful)
When asked, 63% say there are too many manual processes involved
when setting pipeline infrastructure. Additionally, 56% say there are no
automated processes for post-deployment activities (scaling or
destroying environments). 55% point to difficulty in creating consistent
CI/CD pipeline environments across various development teams, and
53% acknowledge that it is challenging to proactively detect
infrastructure issues (such as software version, security patches, and
passwords during testing) in their CI/CD environments. These
challenges slow down a process designed to automate and speed up application delivery,
many times creating friction between Developers and ITOps teams.
63%
4
CloudBolt Industry Insights Report:
The Truth About DevOps in the Hybrid Cloud Journey
11%
"We Love CI/CD…We Just Can't
Completely Rely On It...Yet"
A key issue is CI/CD infrastructure reliability. Failure in the infrastructure across any related
dimension of compute, storage, and networking causes an entire CI pipeline to fail and the
whole process must start over from the beginning. This creates an inordinate amount of waste
(time, processing, resources, et al).
And while 97% of respondents agree that testing CI/CD infrastructure is
important and 85% claim to regularly test that infrastructure, only 11% of
companies actually believe their CI/CD infrastructure is very reliable.
69% characterize it as only somewhat reliable, and fully 21% say theirs is
somewhat unreliable or not reliable at all.
So, what stands in the way of truly reliable CI/CD infrastructure?
Respondents point to a variety of issues, but they primarily boil down to three major factors –
lack of automation, lack of consistency, and lack of proactivity.
