Capture a post-release baseline
Run the standard benchmarks against a finished release and record a reproducible baseline for future comparison.
Use this when
Use this immediately after a release when future regressions or improvements need to be measured against the exact version now in production.
How it runs
- Confirm every in-scope release is complete and record the production revision or artifact identity.
- Run the standard benchmark suite under its documented environment, data, warm-up, and repetition rules.
- Investigate invalid or unstable runs, then rerun only under the same documented conditions.
- Store the final results with the release identity and benchmark metadata, and mark them as the new comparison baseline.
Done when
✓ The new baseline belongs to the completed release. Revision, environment, benchmark version, conditions, and results are recorded together.
Why it works
Tying the baseline to a verified release creates a trustworthy reference point for later performance and quality work. Recording the conditions prevents unrelated environment changes from masquerading as product changes.
Implementation note
Do not overwrite the previous baseline until the release identity and benchmark run are verified. Keep historical baselines available for trend analysis.
More devops loops
Check whether the deploy finished and summarize what changed
A 5-minute watch loop that polls whether a deploy has finished and, once it lands, summarizes what changed. It is a read-only status watcher rather than an agent driving toward a finish condition.
Deploy-poll loop
A hands-free ops loop that polls your deploy every two minutes, runs the smoke test the moment it goes live, and stops with a report if any check fails.
Docker image slimming
Iteratively shrink a Docker image under a size target using multi-stage builds, smaller base images, and layer cleanup, verifying the container still boots each turn.