Skip to content
beskid Beskid

Beskid

Jump to a Beskid service

Beskid

Jump to a Beskid service

Verify Production Delivery

Keep registry and production credentials in their secret managers. Do not print, commit, copy, or put a token on a command line. Woodpecker may publish platform images, but it cannot start, replace, or roll back production containers. Watchtower is the sole automated reconciliation authority.

Prerequisites

Section titled “Prerequisites”

Confirm the Woodpecker publication came from main, was not a pull request, and consumed successful Linux, macOS, and Windows build evidence. Confirm the production host is authenticated to cr.beskid-lang.org and Watchtower is healthy.

Actions

Section titled “Actions”
  1. Open the successful Woodpecker publication for the intended main commit.
  2. Record its build URL, full source SHA, and three successful native build results.
  3. Verify that its image manifest contains five immutable digest records matching the source SHA.
  4. Confirm all five immutable tags exist as cr.beskid-lang.org/beskid/<lane>:sha-<full-sha>.
  5. Confirm each controlled production tag resolves to the intended image.
  6. Inspect Watchtower logs for a successful reconciliation of website, learn, tracker, nexus, and pckg.
  7. Run the signed-in public route and internal container checks documented in Health and monitoring.
  8. Record the immutable tag, reconciliation timestamp, and verification result for each service.

Expected result

Section titled “Expected result”

The recorded Woodpecker source SHA matches every immutable image tag, Watchtower reports the corresponding reconciliation, and each required public route and internal container check is healthy. No CI job performed a production container action.

Recovery

Section titled “Recovery”

If publication or health verification fails, preserve the Woodpecker URL, source SHA, finalized image manifest when present, Watchtower window, and failed endpoint status. Promotion and promoter-cleanup failures occur after manifest finalization, so use that artifact to identify any partially advanced tag set. Pause Watchtower if continued reconciliation is unsafe. The production operator can retag the last known-good immutable sha-* image as production; CI has no authority to perform that recovery. Repeat the production health checks afterward.

Next task

Section titled “Next task”

Verify health and monitoring evidence.