Visualise performance impact between deploys
We’ve introduced a way to track performance between deploys to ensure high quality while shipping new code to any environment.
Learn more about Deployment Tracking and try it out. We are already working on more features—let us know if you have feedback or ideas.
Why track deploys?
As your team pushes out new code it can be difficult to pinpoint which change caused a performance regression. By tracking when new code is deployed, you’re able to visualise potential issues quickly and efficiently.
This leads to teams having more confidence around releasing changes, and less time figuring out when something went wrong.
With Deploy Tracking, every chart shows deploys alongside performance metrics so you always have clarity on what happened and when:
How to get started with Deploy Tracking
Deploy Tracking is available on all plans and is straightforward to implement. Deployments can be created using either our command line client, Node.JS API or a simple HTTP POST.
Command line client
Using CLI 2.0.0+, you can leverage the
calibre site create-deploy --site=site-slug
Deploys can be enriched by using additional flags for Revision, Repository and the Username of the person who initiated the deploy.
calibre site create-deploy \ --site=site-slug \ --revision=7d9580a \ --repository=https://github.com/username/repo \ --username="Clegane the Deployer"
To learn how to implement using our Node.JS API, or via HTTP POST, check the Tracking Deployments documentation page.
We’re using deploy markers when we deploy Calibre—it has already opened our eyes to issues that would have affected our customers.
In the future, we will be introducing automatic detection of problematic deploys, deploy comparison views and much more.