Kofi E. Ampaabeng

Selected Work

20 systems I have architected, built and run: enterprise platforms, consumer apps, and the tools and infrastructure behind them. 20+ years across regulated banking, data platforms and applied ML.

20
systems
6
enterprise
7
ML · LLM
20+
years

18 · CI, registry, rollback

Release pipeline

Build once, deploy by digest, roll back without a person.

Shared pipeline templates test and build an image once, deploy it by digest to a test line that rolls itself back on a failed check, and promote to production by a manual step with its own rollback.

  • Infrastructure

Surfaces

  • CLI
  • Self-hosted
  1. 01Shared templates — Go and Node services include one template that tests, builds rootless and pushes.
  2. 02Deploy by digest — the deploy host takes only an exact digest, waits up to five minutes for ready, and restores the previous image otherwise; its key can run nothing else.
  3. 03Test line, then promote — a manual promotion to production, with a separate rollback job.
  4. 04One-click promote (on a branch) — gate, promote, check, roll back on failure and report, in one job; not yet on the main line.
  5. 05CalVer tags — the next vYY.M.PP for each image is planned from the registry.
  • 12 estate pipeline jobs
  • 3 shared templates
  • 2 registry kinds
SurfacesCLISelf-hosted
SOURCEBUILDREGISTRYTEST LINEPRODUCTIONincludepushpullgateon failureRepositoryShared templatesTestsRootless buildBuildKitRegistryby digestDeploy by digestauto rollbackVerify jobsPromotemanualRollback
Architecture, drawn from the codeServiceStoreModel usedModel trained hereFeedback
  • GitLab CI
  • BuildKit (rootless)
  • Container registry
  • Podman
  • Bash
  • SSH forced command