Why does a continuous process matter?

As the DevOps team continues to support the old and new release pipelines, the technical debt continues to grow. With every service that is onboarded, the DevOps team becomes more of a bottleneck for developers.

The original goal of the pipeline was to be able to release as often as the developers would want. But with the major restructuring of the delivery and deployment because of the business requirements, the quality and development teams were getting in each other's way. The new development process consisted of a developer triggering a code merge with the main source code branch whenever a new piece of code was written. Since every code change was resulting in the integration process being triggered, the development team was producing release candidate artifacts faster than the quality team could check. This resulted in a large set of artifacts waiting to be deployed into the testing environment. The quality team had to reduce test...