Hear when a deploy fails

What is told

• A failed deploy or rollback: the command ended with an error.
• A deploy whose machine went quiet: it stopped reporting for 10 minutes before it said how the deploy ended, and is now lost.

A good deploy, one stopped with Ctrl-C and one closed by hand on its page tell nobody. Each notice is sent once.

By e-mail

Until you say otherwise, each of the project's people who can open Deploys gets an e-mail. The people are the project's members at id. The project's Settings in Deploys lists who that is now, under Notices.

Other addresses, such as a team's shared inbox, are added on Settings → Notices, below.

Telegram and Slack

The project's chats and channels are set once for every product, on Settings → Notices:

• Destinations: e-mail addresses, a Telegram chat (its chat id, and a bot token unless the service's own bot sends), or a Slack incoming webhook.
• What goes where: for Deploys, a row for each kind of notice, ticked against each destination and the project's people.

Once you tick anything for a kind, its notices go only where you ticked, so tick the project's people too to keep their e-mails. Bot tokens and webhooks are kept encrypted.

What a notice says

The first line says what broke and where. The next says the project, who ran it from which machine, the commit and branch, the release and how long it ran. Then come the end of the log and the link. By e-mail, with the subject [failed] shop production: Deploy #12 · Storefront:

✖ shop · production: Deploy #12 failed (exit code 2)

Storefront · by Anna Virtanen on anna-mbp · a1b2c3d4 on main · release 20261101-101500-a1b2c3d · ran 1m 32s

The end of the log:
  ==> Running migrations
  SQLSTATE[42S01]: Base table or view already exists
  make: *** [deploy] Error 2

Open: https://services.my-beast.com/acme/storefront/deploys/apps/shop/deploys/12

An e-mail carries the last 12 lines of the log, Telegram and Slack the last 6. A lost deploy's notice says to look on its machine or on the server.

Send a test

In the project's Settings in Deploys, Notices has Send a test, for the project's admins. It sends a test notice to every destination the project has, and an e-mail to you, so a wrong chat id or webhook shows now rather than when a deploy fails.

Was it sent?

A deploy's page lists the notices sent about it under Told: each e-mail, chat and channel, and whether it went, with the reason when it didn't. One destination failing never stops the others. The latest sends to Telegram and Slack are also in Deploys' part of the project's Settings. Troubleshooting has more.