Description
Key Stakeholders:
DevOps Evangelists, Platform Engineers, Release Managers, Automation Architects, Software Developers, Software Testers, Security Engineers, Software Engineering Directors and Managers. CIOs, CTOs, VP of IT, IT directors
Why It Matters:
The market for continuous integration and continuous delivery/deployment is rapidly evolving. Understanding the process, projects, vendors, and market landscape will help in “buy versus build” decisions and the design of CI/CD workflows.
Top Takeaway:
The CI/CD market is evolving rapidly in a symbiotic fashion with the cloud native, container cluster market. Presently, toolchains tend to be a DIY affair. This limits the reach of full CI/CD automation to companies with the resources to integrate products themselves. In response, end-to-end solutions are quickly emerging as vendors attempt to offer as much of the CI/CD toolchain as possible. The result will be to democratize CI/CD.
Amalgam Insights recommends pursuing end-to-end solutions except in unusual or very complex environments. It makes the most sense to use a cloud service providers’ toolchain if operating in a purely cloud environment. For any environment with an on-premises component, or in multi-cloud situations, toolchains that can deploy on-premises and to multiple cloud services are preferred; otherwise there is the risk of rip-and-replace later to accommodate new cloud services. Similarly, even if Kubernetes is not part of an environment now, the CI/CD toolchain should support it so that it is futureproofed.