How Statuspage deploys continuously with Bitbucket and Sleuth
Jun 4, 2021Kelvin Yap

Summary
This post details Statuspage's continuous deployment process, emphasizing the use of Sleuth for deployment coordination and health monitoring. It describes how Sleuth's 'locking' feature prevents merges outside designated times, improving developer sanity and preventing production issues. It also explains how Sleuth aggregates error and metric data from tools like Sentry and SignalFx to provide a unified view of deployment health, allowing developers to quickly identify and address unhealthy deployments.
More from the Deployment Orchestration and Health Monitoring trail
- Introducing the redesigned deployments experience
- Custom deployment permissions for your environments (Beta)
- Track Deployment status for your PRs (Beta)
- OpenTelemetry traces for Bitbucket Pipelines via webhooks
- Pull request intervention for infrastructure-as-code risks with Bitbucket custom merge checks