Work as a team
Sign-off from affected teams
When a release changes or breaks the calls other teams make, those teams are asked to sign off before it moves; every answer and every move without one is recorded.
Open Deployments in the appWhat it asks
When a release of a system moves to an environment, Rabbinatix compares what that environment runs now with what it will run after the move. Every other system whose calls to it change shape, break, or lose an API they call is affected, and the team that owns each one is asked to sign off. A system with no team is listed under No team to ask.
It is asked whichever way the move happens: a move request in the app, a pipeline calling POST /v1/deployments, or a deployment recorded by hand.
Per environment
Each environment says what to do, next to its approvals in Settings:
- Off: nothing is asked.
- Ask: the teams are asked and every answer is recorded; the move goes ahead whatever they say. This is the default for Production.
- Require: the move waits until every affected team signs off, or someone who may move releases presses Move anyway with a reason (it never blocks for good: the move records the teams it went without).
Answering
A team lead (or whoever covers for them) answers for the whole team:
- Sign off: the change is fine for us;
- Not yet, saying what has to happen first;
- Not affected, saying why.
The request shows what changes for the team: its systems and the calls that change or break. The asking team is told about each answer. An answer is due after two working days, or after the days the teams agreed in a team promise ("Sign-off answered within").
What is recorded
The move request and each deployment keep the teams asked, each answer with who and when, and the teams it moved without, with the reason. Activity says, for example, Moved without sign-off and names the teams. A move without a team's sign-off also raises a team issue against the moving team.
From a pipeline
GET /v1/can-i-deploy shows sign-off as information, and refuses only where the environment requires it. POST /v1/deployments refuses a release that waits for sign-off unless the body says why: "allowMissingSignoff": "hotfix for the outage". The reason is recorded as if someone pressed Move anyway.
Related
- Environments and deploymentsRecord which release of each system runs in each environment, see compatibility per environment, and check a release before you deploy it.
- Team promisesWhat one team promises another for a system: uptime, response time, notice before breaking changes, how fast a service is fixed, how fast sign-offs are answered — agreed by both, measured by Rabbinatix.
- Time awayMark when people are away, add public holidays, and pick who covers, so sign-offs and team issues reach someone who is here.
