A company has a CI/CD pipeline implemented to automate application deployment. An urgent change is required in the production environment. A developer produces and tests the required change in the com

Removing a failing test is an anti-pattern that bypasses quality gates, undermining the purpose of CI/CD and leading to potential deployment of broken or unstable code.

Manually deploying changes bypasses the CI/CD pipeline's automation, quality checks, and audit trail, violating CI/CD principles and introducing significant operational risk.

Using a backup pipeline doesn't address the root cause of why the primary pipeline is failing with the change; it's a workaround that doesn't solve the underlying validation issue.

A core principle of CI/CD is environment consistency, where testing in an environment that closely mirrors production reduces deployment risks. Replicating the production environment within the pipeline ensures that tests validate changes against conditions identical to production, identifying and resolving issues before deployment and allowing the pipeline to pass reliably.