However, the report also found that code velocity has remained steady for the past two years, with about 15% of teams being considered top performers, meaning they have lead times of less than one day.

The CDF believes that while DevOps may be a help, it is likely the increasing complexity of projects that is slowing things down. 

Another finding in the report is that despite the increase in DevOps adoption, there hasn’t been an increase in the number of DevOps-related tools over the last year. The average number of tools sits at 4.5 currently. 

However, there is still a strong correlation between the number of tools in place and how likely a team is to be a top performer. These top performers were measured by three metrics: lead time for code changes, deployment frequency, and time to restore service.

The report also found that in general increasing CI/CD tools may increase performance, but interoperability concerns arise when multiple tools are used together. 

“We note that the proportion of top performers remains flat while that of low performers increases dramatically, with an increasing number of self-hosted CI/CD tools used. This suggests that there is a diminishing return from increasing the number of CI/CD tools a developer uses. The usage of an increasing number of tools may also be a response to increased complexity, which is having negative impacts on the performance of these developers. Similarly, the integration of multiple tools may not be optimally implemented, leading to function overlap that is impacting performance,” the report states. 

The report also shows a correlation between speed and stability metrics. 30% of the highest performers in code change lead time were also the highest performers when it came to service restoration. 

Interest in security is also clear from the survey, as testing applications for security measures was done by 37% of developers, rising up to the second most popular DevOps-related activity that teams engage in. 

“Developers who perform build-time security checks in an automated and continuous fashion are the most likely to be top performers, and the least likely to be low performers, across all

three metrics, of the types shown,” the report states. 

The report was conducted in partnership with SlashData, surveying over 125,000 respondents. It was released during the Linux Foundation’s Open Source Summit, happening this week in Vancouver, BC. At the event, the CDF also announced the addition of four new members: F5 NGINX, Prodvana, Salesforce, and Testkube.

The post Report: Adoption of DevOps practices increasing, while code velocity remains the same appeared first on SD Times.

According to The Linux Foundation’s 2021 Open Source Jobs report, 88% of technology professionals utilize DevOps, which highlights the importance of understanding these practices. 

The Linux Foundation and CDF designed the bootcamp to be for existing or aspiring developers, operations professionals, engineers, or anyone else involved in software development, delivery, deployment, and maintenance. 

The DevOps Bootcamp will provide an introduction to areas like DevOps and Site Reliability Engineering (SRE). It also gives more detailed information into specific DevOps toolsets, such as Jenkins, then the course finishes off with advanced topics, such as GitOps and DevSecOps. 

The foundations also noted that while the program talks about specific tools like Jenkins, it’s not intended to train students on those toolsets. This is because there are many DevOps tools out there and many organizations use a combination of tools, so it is better to take specific training on those tools as needed.  

In addition to the classes, students will get access to an online forum where they can interact with other students, as well as virtual office hours with instructors four days a week.  

The program can be completed in six months if a student dedicates 10-15 hours of effort per week to it, according to the foundations.  

“Implementation of continuous delivery techniques varies widely by industry and requires case-by-case understanding of your own unique development environment. The Linux Foundation continues to provide high quality courses for software developers who want a better understanding of the continuous delivery landscape, and this DevOps Bootcamp is an excellent way to turbocharge your understanding and proficiency,” said Tracy Miranda, executive director of the Continuous Delivery Foundation. “By enrolling in the DevOps Bootcamp, within just a half year, you will be able to better evaluate and implement a solution that meets your DevOps needs.”

The post DevOps Bootcamp launches to reduce barrier to entry for technology roles appeared first on SD Times.

One place to look is the Continuous Delivery Foundation (CDF) which is home to many of the fastest-growing CI/CD open-source projects. The CDF fosters vendor-neutral collaboration among developers, end users and vendors to further best practices and industry specifications. DeployHub CEO and co-founder Tracy Ragan, who serves as the CDF general membership board representative, provides additional insight in this Q&A.

RELATED CONTENT:
CI/CD pipelines are expanding
CI/CD success requires a sound approach
How some organizations are implementing CI/CD

SD Times: Why was the CD Foundation formed?
Ragan: We are on the top of a swell that is turning into a massive tsunami when it comes to software development. According to “The Future of Employment: How Susceptible Are Jobs to Computerisation?” by Carl Benedikt Frey and Michael A Osborne, 47% of U.S. jobs may be replaced by AI. If this is true, we have lots of software to develop over the course of the next 20 years and our current CI/CD process will not be able to sustain this massive amount of software development and management. For most organizations, CI/CD is a workflow orchestration tool that calls scripts. In most cases, the scripts do the heavy lifting of the movement of code through the process. In order to build the software of tomorrow, CI/CD must do better, be more automated and include more than just “check-in and build.”  And we are moving from monolithic software to microservices. This directly impacts the CI/CD process. The time is now for the CI/CD community to have a conversation about what CI/CD looks like today (terms and definitions) and where it is headed tomorrow (Kubernetes pipelines, AI/MLOps). 

What does the organization hope to accomplish?
 We have 9 strategic goals:

1. Drive adoption
2. Cultivate growth of open-source projects
3. Foster tool interoperability
4. 4Champion diversity and inclusion
5. Foster community relationships
6. Grow the member base
7. Create value for all members
8. Promote security as a first-class CI/CD citizen
9. Expand into emerging tech areas.

In what ways will the CD Foundation help organizations improve the efficiencies and effectiveness of their CI/CD practices?

The CD Foundation provides a platform and thought leadership community for driving CI/CD to the next level. The CD Foundation’s job is not to produce a CI/CD “stack” or best practices guidelines. CD is too broad to have a single solution for all. The CD Foundation’s job is to bring members together to achieve our 9 strategic goals and provide a vendor-neutral platform for open-source tools that fit into the CI/CD landscape.

 What impact might the initial and future projects have on CI/CD tools and tool chains going forward?
 While it’s hard to predict the impact today, we are beginning to see more productive discussions between projects. Jenkins and Spinnaker are working to define how they interoperate. There is community discussion around Tekton and JenkinsX. Most organizations will have a variety of different pipeline orchestration tools (Jenkins, Tekton, CircleCI, Bamboo, Spinnaker, etc). And most companies will allow individual teams to decide on what those orchestration tools will call. Not all teams will look the same. A mix of open source and commercial will continue to be the way new tools are adopted and implemented. What the CD Foundation can offer is a platform for managing the open-source tools and foster discussion between the teams. Our third most important goal is to “foster tool interoperability.”  If we are successful, we will have achieved the ability for one orchestration tool to call another. Developers might use Jenkins while Production Control is using Spinnaker. 

What does the future of CI/CD look like?
in the future, CI/CD will grow in importance as developers are pushed to create more software. We now talk about moving software through the lifecycle faster, tomorrow’s discussion will be around sustaining the number of new applications hitting the market. So fast is important and CI/CD is a key player in ‘faster’ and ‘more’.

 From a lower level, if we look at microservices, our CI/CD process changes. First off, version control becomes less critical. We will not have source code that is several thousands of lines of code long that requires branching and merging to allow multiple developers to work on it at the same time. We will instead have code that is hundreds of lines long at max. When you think of microservices, you must think functions.

 Second, compiling code may not be required. While Go is compiled, Python is not. And even if it is compiled, it will be quick – no more long builds and no linking.

Third, microservices are “loosely coupled.”  This means no linking at build time. APIs at runtime replace a build “link” step. The concept of an “application” built all at once goes away. 

Our CI/CD pipelines will be managing thousands of individual microservice workflows. Today we generally have one workflow per application, tomorrow we will have one workflow per microservice.

Deployments will always be incremental. Deploying a full application will no longer happen. A new microservice will be updated, creating a new version of the “logical” application. An application is just a collection of services.

And finally, configuration management will be needed to map a collection of microservice versions back to a logical view of an application version and to track which applications are using which service.  

So yes, lots of changes are coming our way, and the CD Foundation is here just in time to help lead the discussion, manage new open-source projects and inspire tool interoperability.

The post The Continuous Delivery Foundation advances CI/CD appeared first on SD Times.