CI/CD / DevOps

One Toolchain to Manage All the Development: A CI/CD-Vendor Obsession

5 Sep 2019 10:28am, by

Measuring CI/CD adoption is difficult for many reasons, but one of them is the choice between all-in-one bundled software or best-of-breed tooling. How thousands of companies and individuals evaluate the trade-offs between these approaches will shape the future of DevOps tooling and what toolchains are used.

A 2019 Forrester study sponsored by GitLab quantified found that more than three-quarters of organizations use at least two software delivery toolchains, with the average organization having six or more tools per toolchain. Based on a survey of 252 IT professionals with responsibility over toolchain management, the study also reported that ensuring security (45%) and visibility into maintenance (39%) are the top process challenges teams face with their toolchain.

Only 18% of the survey has an out-of-the-box software delivery solution that integrates a toolchain from end-to-end. The study was conducted because GitLab is interested in being one of these solution providers. It is not alone in the rush to consolidate and simplify software delivery tools. For example, the CloudBees acquisition of Electric Cloud is explained as an attempt to provide integrated developer toolchains. Just this week, TPG Capital acquired CollabNet VersionOne, which has been described as the next step in an “arms race” to provide a DevOps platform that is bundled and sold as value stream management.

A toolchain can perform a limited amount of functionality or enable all steps in the software development lifecycle (SDLC). Even when a company has an end-to-end solution, it may only be adopted by some teams and for specific use cases. When integrated, they become a toolchain. When toolchains are integrated, the term is synonymous with “pipeline,” “value stream,” or any other description of a bundled system to build, test, deliver and monitor software.

In practice, companies use a combination of commercial off-the-shelf software (COTS), open source and homegrown tools that have to be integrated. Plug-ins and APIs can make the process easy, but there is a constant risk that customization will introduce technical debt, and high support costs. The 2019 Accelerate State of DevOps report shows that most people use a wide range of these integration approaches. Twice as many (43%) of the worst performing DevOps companies use a heavily customized mix of COTS, open source and in-house software, as compared to the rest of the study that only does so 22% of the time.

Source: 2019 Accelerate State of DevOps

GitLab and CloudBees are The New Stack sponsors.

Feature image via Good Free Photos.

Participate in The New Stack surveys and be the first to receive the results of our original research.