{"id":18724,"date":"2020-05-20T03:02:44","date_gmt":"2020-05-20T03:02:44","guid":{"rendered":"https:\/\/rbsitsoftwaresolution.com\/blog\/gitlabs-take-on-the-current-state-of-devops.html"},"modified":"2020-05-20T03:02:44","modified_gmt":"2020-05-20T03:02:44","slug":"gitlabs-take-on-the-current-state-of-devops","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/gitlabs-take-on-the-current-state-of-devops.html","title":{"rendered":"GitLab’s take on the current state of DevOps"},"content":{"rendered":"

<\/span><\/p>\n

\n\t\tSpecial Report<\/span>
\n\t<\/h3>\n


\n <\/span><\/p>\n

<\/a><\/p>\n

\n
\n Riding the DevOps revolution
\n <\/a>\n <\/p>\n

You can download all of the articles in this special report in one PDF (free registration required).<\/p>\n

\n Read More<\/a>\n <\/p>\n

GitLab<\/a>, a prominent Git<\/a>-based DevOps<\/a> company, has released the results of its fourth annual DevSecOps survey<\/a> This global survey of over 3,650 respondents found that DevOps rise has led to “sweeping changes in job functions, tool choices, and organization charts within developer, security and operations teams.”<\/p>\n

The vast majority of developers are finding DevOps is living up to its promise of faster software releases. According to the survey, nearly 83% of developers report being able to release code more quickly with DevOps.\u00a0<\/p>\n

Continuous integration and continuous delivery (CI\/CD<\/a>) is also reducing build and deployment times. Thirty-eight percent said their DevOps implementations include CI\/CD. Of those using CI\/CD, nearly 60% deploy multiple times a day, once a day, or once every few days. That’s up considerably from last year’s 45%. Twenty-nine percent also said their DevOps implementations include test automation.<\/p>\n

George Tsiolis, Ubitech<\/a> engineering lead and GitLab core contributor, added:<\/p>\n

\n

“Over the last year, Ubitech introduced CI\/CD practices to multiple teams for new and existing projects within the organization. So far, implementing CI\/CD has led to an overall boost in test coverage efforts and more frequent deployments. It’s also given our team new insight we needed to spot potential vulnerabilities before and after deploying our applications.”<\/p>\n<\/blockquote>\n

Testing, however, is still a major bottleneck. Forty-seven percent reported that testing was the area most likely to cause delays. True, automated testing is on the rise, but only 12% claim to have full test automation. And while 60% of companies report deploying multiple times a day or once a day, over 42% of those surveyed said testing still happens too late in the development lifecycle.<\/p>\n

DevOps itself is living up to its promise of blurring the lines between developers and operators. Thirty-five percent of developers say they define and\/or create the infrastructure their app runs on — with 14% monitoring and responding to infrastructure issues.\u00a0<\/p>\n

DevOps adoption rates are also up. Twenty-five percent of companies are in the DevOps “sweet spot” of three to five years of practice, while another 37% are well on their way, with between one and three years of experience under their belts.\u00a0<\/p>\n

\n<\/section>\n

As you’d expect with numbers like that, roles across software development teams are shifting as responsibilities overlap. 70% of operations professionals report that developers can provision their own environments.<\/p>\n

That’s good news. But, while DevOps is enabling businesses to dramatically increase their software release times and moves to truly continuous integration\/deployment (CI\/CD), it’s not all sunshine and kittens.\u00a0<\/p>\n

Sid Sijbrandij, GitLab’s CEO and co-founder, said in a statement: “There is still significant work to be done, particularly in the areas of testing and security. We look forward to seeing improvements in collaboration and testing across teams.”<\/p>\n

You see, it’s not just a changing world for developers and operators. Security and testing teams also need to be brought into the DevOps world.\u00a0<\/p>\n

The survey found a real disconnect between developers and security teams. The problem — and this is an ancient one — is no one’s sure who’s really in charge of security. More than 25% of developers reported feeling solely responsible for security, compared to testers (23%) and operations professionals (21%). On the security team side, 33% of security professionals said they’re in charge, while 29% said they believe everyone should be responsible for security.<\/p>\n

Specifically, security teams say developers are not finding enough bugs in development’s early stages of development. Over 42% said testing still happens too late in the life cycle, while 36% reported it was hard to understand, process, and fix any discovered vulnerabilities, and 31% found prioritizing vulnerability remediation an uphill battle.\u00a0<\/p>\n

Johnathan Hunt, GitLab’s vice president of security, stated, “Security teams need to implement concrete processes for the adoption of new tools and deployments in order to increase development efficiency and security capabilities.”<\/p>\n

So, there’s still work to be done with DevOps. That said, DevOps is well on its way to becoming the new way IT staff not only develops but operates their systems.\u00a0<\/p>\n

Related Stories:<\/strong><\/h3>\n