Deploy locks & deploy blocking

Claim a destination before you ship. The team can see who's holding it; deploys to it stay paused until it's released.

How locks work

A lock is held against a single destination on a single application. While locked, anyone looking at Shipyrd or the destination’s Slack channel can see who has it and when they took it. The lock is owned by a Shipyrd user — typically the person who’s about to deploy.

A lock gets created in one of two ways:

  1. Manually, from the dashboard or from Slack (/shipyrd lock my-app production).
  2. Automatically, when a destination opts in to office hours — Shipyrd locks it outside the hours your organization is online.

A lock is released when its holder unlocks it (from the dashboard or /shipyrd unlock my-app production), or — for office-hours locks — when the destination re-enters business hours.

Locking from Slack

If you’ve installed the Slack bot, you can lock and unlock without opening Shipyrd:

/shipyrd lock my-app production
/shipyrd unlock my-app production

The bot posts to the channel so the rest of the team can see who’s holding what. /shipyrd status shows every lock across the organization.

Lock state in badges

The lock status of a destination is exposed via a public deploy badge, so READMEs and status pages can reflect it without anyone opening Shipyrd.