Three facts stood out: DevOps speeds up release times and improves code quality, but it has also dramatically changed the roles and responsibilities of developers, operations pros, security team members, and testers.
Here's what you need to know.
That’s up from 45% last year. In other words, DevOps brings truly continuous deployment.
Over 25% of companies are in the DevOps “sweet spot” of three to five years of practice. And another 37% are well on their way, with between one and three years under their belts.
It's DevOps FTW The majority of respondents said code quality was the biggest benefit of choosing DevOps.
The majority of respondents aren’t using Kubernetes and microservices yet, but they are investigating them.
Today 47% of companies say testing is the number one reason for delays. That’s down slightly from last year’s survey.
66% of respondents say their organization’s processes and tools allow them to succeed and innovate.
“ Pre-deployment tests have provided more confidence that the product is ready to be released; also delivery frequency has increased. ”
Most report two to five times increases although one developer said his team was “light years ahead.”
Last year, respondents told us they wanted to invest in their DevOps processes. And they did. The top three areas for investment this year: CI, SCM, and test automation.
Devs are nearly unanimous in the need for their organizations to do more testing. Apparently, you can’t have too much testing.
It depends on who you ask. But, more than 25% of developers feel solely responsible for security, indicating that shifting security left has begun in earnest.
Love it or hate it, they’re doing it, a lot. Most do code reviews weekly, but many said their organizations are moving to a daily cadence.
Thanks to DevOps automation improvements, developers are happy to report they no longer have to deal with annoying “manual” tasks like testing and deployments.
Respondents were asked to rate their organization’s DevOps processes based on organization, repeatability, and scalability.
Respondents were asked to rate their organization’s DevOps processes based on organization, repeatability, and scalability.
“ We reduced our CI build queue time by 75%, which allowed developers to have test results faster and allows QA to have build artifacts to test faster. ”
If you want to enable developers to find and fix vulnerabilities, you have to give them the scan results in their pipelines or native workflows.
Sec pros report that their orgs are shifting security left, but they really aren’t doing the scans to support that claim.
Just like in last year’s survey, security pros think devs don’t find enough of the bugs at the earliest stages and are slow to prioritize fixing them.
Most sec teams don’t have security processes in place for microservices/containers/APIs/cloud native or serverless.
Almost 33% of security respondents said they were responsible for security. But nearly as many, 29%, said everyone was responsible for security. Clarity is needed.
Over 42% said testing happens too late in the lifecycle, 36% reported it was hard to understand, process, and fix any discovered vulnerabilities, and 31% found prioritizing vulnerability remediation an uphill battle.
Respondents were asked to rate their organization’s DevOps processes based on organization, repeatability, and scalability.
We’re excited, but it’s important to note that 60% of survey respondents are GitLab users.
“ (Security) is becoming less focused into silo positions and more of a Jack of all trades role. ”
Over 60% report new and different responsibilities because of DevOps.
Almost 40% of operations team members said their development lifecycle is “mostly” automated.
Almost 70% of ops pros report that devs can provision their own environments, a sure sign of shifting responsibilities brought on by new processes and changing technologies.
Over 21% of ops pros say they feel solely responsible for security in their organizations.
Respondents were asked to rate their organization’s DevOps processes based on organization, repeatability, and scalability.
We’re excited, but it’s important to note that 60% of survey respondents are GitLab users.
“ [Operations today] is 60% new project work and 40% operations/fire-fighting/developer support. ”
despite advances in automation their teams are the same size they were last year.
About 33% of testers report closer (and presumably happier) collaboration with developers than ever before.
Just 12% claim to have full test automation.
Almost 75% of testers say their orgs have shifted testing left (meaning closer to development).
Almost 60% said their teams are the same size they were last year, despite advances in automation.
A small but intriguing percentage of test teams (16%) either use “bots” to review their code or have an AI/ML tool in place for testing.
23% of testers think they’re solely responsible for security in their organizations.
Respondents were asked to rate their organization’s DevOps processes based on organization, repeatability, and scalability.
We’re excited, but it’s important to note that 60% of survey respondents are GitLab users.
“ We do TDD. QA and dev act as a team. We have automated tests running parallel with developing code. ”
Chart your course in a rapidly changing technological landscape to move your teams towards greater collaboration and velocity.
You will also receive a link to the report to your inbox shortly.
Your thoughts in this survey shape how we build products to help teams strengthen collaboration, iteration, and delivery.
