Source: thenewstack.io
CI Observability for Effective Change ManagementCategory: Software
This is more profound than ever when thinking about software development pipelines.
Every step in releasing software to production is interlinked, and this means an expanded range of constraints.
This is because change management is abstract and often believed to slow down deployment in production.
On the other hand, tests and their success or failure to communicate potential harm depends on those who write tests and how the CI tool executes tests, and this is where a major problem arises: The phenomena of flaky tests.
In an attempt to ditch conventional and strenuous change management practices, relying on CI tests is crucial, but as discussed above, we need to ensure confidence in the way we perform these tests.
Every step in releasing software to production is interlinked, and this means an expanded range of constraints.
This is because change management is abstract and often believed to slow down deployment in production.
On the other hand, tests and their success or failure to communicate potential harm depends on those who write tests and how the CI tool executes tests, and this is where a major problem arises: The phenomena of flaky tests.
In an attempt to ditch conventional and strenuous change management practices, relying on CI tests is crucial, but as discussed above, we need to ensure confidence in the way we perform these tests.
Related Articles
Community Partners
DevOps Careers