Most conversations about CI/CD reliability start in the wrong place. Teams debug flaky pipelines, investigate intermittent failures, tune alerting thresholds and optimize build times. All of that work is legitimate. However, the decisions that most directly determine whether a CI/CD pipeline is reliable or not were made months or years earlier, during tool selection. By the time teams are debugging pipeline reliability, they are usually dealing with the downstream consequences of upstream decisions that seemed reasonable at the time. The software development tools a team chooses shape their CI/CD pipeline in ways that are not always visible during evaluation. Understanding those connections is the most practical starting point for teams that want reliable pipelines rather than better pipeline firefighting. The Integration Surface Problem Every tool in a software development stack creates an integration surface. Integration surface is the set of connections a tool has with oth...
New Relic will provide free access to the entire New Relic One observability platform for 90 days to any organization engaged in COVID-19 pandemic relief efforts that have a specific benefit to the public. Erin Dieterich, director of corporate social responsibility at New Relic, said it’s apparent that the IT platforms of both nonprofits and […]
Comments
Post a Comment