One runlist, in order
Every step from every team, in the order the deploy runs, with what each step waits for and whether it can start.
Rubber duck deploys.
Rubber duck debugging is talking your code through, step by step, until the problem shows itself. DeployLogs does that for a deploy: every team's steps in one runlist, walked through in a practice run before the night it counts.
A deploy runlist and go/no-go tracker for Google Sheets, for deploys that cross teams.
Deploys fail in the gaps between teams
One team runs sprints, another keeps its steps in someone's head. One system creates the IDs the next team needs, and nobody wrote that down. An estimate nobody has run becomes the plan. DeployLogs puts every team in one runlist, in the order it runs, held to the same rules.
What it does
Handoffs between teams
When one team creates something the next team needs, the value shows up on the step that is waiting for it.
Estimates with a source
Every estimate is marked Practiced, Owner's guess or Missing. Practice runs replace guesses.
Go or no-go
Each stage ends at a gate every team signs. The overview shows the latest time it is safe to keep going, with the rollback counted.
Smoke tests and sign-off
Every change has a smoke test and a named person in the business who signs off the result.
Lock, log and close
Lock the tracker for the run, record every edit, and close it out as the record of the deploy.
Where it is today
DeployLogs is in testing and not on the Google Workspace Marketplace yet.
Now
Built and in testing
- Runlist, waits and handoffs
- Estimates and plan hours
- Stages, gates and the overview
- Changes, smoke tests, data migration
- Lock, audit log, close out
Next
Being designed
- Steps that stop the deploy if they fail
- A freeze window
- Practice runs that record their own times
- Results after go-live
Later
Ideas
- Fill the runlist from Jira
- Google Workspace Marketplace