Deploys · Guides
See what is live
What is live in an environment is the last deploy or rollback there that ended well. Deploys shows it per app, on the overview, in the terminal and beside the other products' pages.
The overview
The project's home in Deploys, for the last 30 days or 7:
- how many deploys and rollbacks ran, and the share of them that failed or were lost;
- how many were rollbacks, and how many were lost;
- how long a good deploy takes, and how long from a failed deploy to the next good one, each the median;
- deploys per day, the good ones beside the failed or lost;
- Apps: what is live in each environment, when it went live and who sent it, and how the last deploy there went;
- Running now, while a deploy runs.
Each figure and each day opens the deploys it counts.
An app's page
Live now has a row per environment: what is live there, the last deploy and how it ended, and where a rollback would go, with its command to copy. Below it, the app's history, newest first, narrowed to one environment if you like. Roll back says more about the rollback column.
History
Every deploy of the project's apps, newest first. Narrow it to the last 7, 30 or 90 days or one day, to how they ended (succeeded, failed or lost, stopped, running), to deploys or rollbacks, to an environment or to an app. Every view has its own address, so you can share one.
From the terminal
mybeast-deploy status prints what is live in an environment and the app's saved commands. It runs nothing:
mybeast-deploy status --app shop --env production
Shop (shop)
live on production: 20261101-101500-a1b2c3d - Deploy #12, by Anna Virtanen, 1.11. 10:16 (2 hours ago)
last deploy there: succeeded
deploy command: make deploy:production
rollback command: make rollback:productionWithout --env it prints the saved commands only, with {env} as they were saved.
In the other products
The project's other products ask Deploys about the moments they show. An issue in Errors, an incident in Incidents or a log in Logs says which deploys went out to its environment from an hour before it, such as Shop #41 went live in production 12 min before, with who ran it and the commit's subject. A failed or lost one is marked as a problem, and each opens its deploy's page.
Find a deploy
The search in the top bar finds a deploy by:
- its commit, from the first 7 characters:
a1b2c3d, - its release, whole:
20261101-101500-a1b2c3d, - its number,
#12, orshop #12when several apps have one, - words of its branch or its commit's subject.
It finds apps by their name or key. It never searches a deploy's log.