Make dev-base image publishing resumable and retryable #565
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os#565
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current dev-base publish path is too brittle for the size and cost of the image family. A transient failure in one tier can force a full retrigger path, and Forgejo cannot reliably rerun failed jobs from this surface.\n\nImprove the image publish workflow without changing the requested release-ref decoupling from issue 564:\n\n* make each dev-base tier independently dispatchable with inputs for sha, tier, tag, mode, and source tag where relevant.\n* before building or retagging a tier, verify whether the exact target manifest already exists and skip it when it is already correct.\n* add a durable per-tier checkpoint signal through package tags, artifacts, or another repo-native marker so a resumed run can continue from completed tiers.\n* add bounded retries around transient operations: registry login, manifest inspect, buildx push, buildcache probe, and promote or retag operations.\n* preserve the tier DAG, but make a rerun cost the failed tier and its dependents, not a full from-scratch release train.\n* make Telegram alerts non-blocking so an alert transport failure cannot mask or create a release failure.\n\nOut of scope: do not add a summarize-publish job, and do not create broad ::error:: diagnostic-message churn as part of this issue.
WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-565on hostkais-macbook-pro-2.local.Accepted by
ward agent --harness codex(reserved 2026-07-15T07:16:13Z). Concurrentward agentruns are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL).--override-reservationoverrides.Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).
run seed context — what this run is carrying (ward#609)
coilyco-flight-deck/agentic-os#565· branchissue-565· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-565· wardv0.697.0· dispatched2026-07-15T07:16:00ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).
— Codex, via
ward agentWARDED_WORKFLOW: #567
details
workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA)
felt: steady, mostly workflow hardening and doc shaping
confidence: high
surprises: the doc size cap forced a second pass
follow-ups: director merge and final done outcome
WARDED_WORKFLOW: blocked 🛑
details
workflow: pull-request-and-merge; review summary: skipped (in-container review gate intentionally skipped because temporary ward default pending brokered QA)
blocker: Forgejo merge stayed on 405 after repeated retries while the PR stayed green
reservation-lock: released and handed back
felt: the implementation landed cleanly, the merge surface did not
confidence: medium
surprises: the only failure left was the Forgejo merge endpoint
follow-ups: retry the merge from a surface with queue access or after the Forgejo merge queue clears
WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-565on host74a70515a491.Accepted by
ward agent --harness codex(reserved 2026-07-15T09:00:56Z). Concurrentward agentruns are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL).--override-reservationoverrides.Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).
run seed context — what this run is carrying (ward#609)
coilyco-flight-deck/agentic-os#565· branchissue-565· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-565· wardv0.710.0· dispatched2026-07-15T09:00:53ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0).
— Codex, via
ward agentWARDED_WORKFLOW: dispatch-deferred
launch failure details
The PR repair run never started.
warded engineer coilyco-flight-deck/agentic-os#565 --harness codex --branch issue-565 --workflow pull-request-and-mergefailed before container creation becauseforgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latestwas unavailable remotely and no local image existed. Docker has noengineer-codex-agentic-os-565container. No repository work was performed.The reservation is released for redispatch from a fresh director. The repair target remains existing green-but-unmergeable PR #567: update
issue-565onto currentmain, preserve the resumable publishing changes, rerun checks, and land it.ward agentCurrent release recovery hit this blocker directly. On release head
d1ca18e7e53ed1918f0f0571f374a53985a21ed9:dev-base-publish.ymlrun1401failed.plan-draftsucceeded.publish-corefailed after 17m17s../actions/publish-dev-base-tier, duration 16m17s.publish-lang-node,publish-lang-go,publish-lang-dotnet,publish-ops,publish-agent, andpublish-fullstayed blocked.PR #567 is green but the brokered merge attempt hit Forgejo 405 "Please try again later". This issue remains on the active release path.
Completed by merged replacement PR #579. It lands the resumable/retryable dev-base publication behavior on current main together with the release-retag wait from #574. Stale PRs #567 and #577 are closed as superseded. Closing this source issue; post-merge main CI run 8428 is tracked separately.