fix: [nomad-step-4] S4-fix-2 — build disinto/agents:latest locally before deploy (no registry) (#972) #973
No reviewers
Labels
No labels
action
backlog
blocked
bug-report
cannot-reproduce
in-progress
in-triage
needs-triage
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
rejected
reproduced
tech-debt
underspecified
vision
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: disinto-admin/disinto#973
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/issue-972"
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?
Fixes #972
Changes
AI Review
Review
The PR adds a
docker buildstep for theagentsservice image before the Nomad deploy loop, for both dry-run display and real execution.Correctness claims verified:
echo ",$with_services," | grep -q ",agents,"wraps in commas to prevent partial matches (e.g.,agents-extra). Matches the same pattern used in the deploy loop at line 941. Correct.docker build ... 2>&1 | tail -5underset -euo pipefail(line 24) propagates docker's nonzero exit; a failed build aborts the script. Correct.Minor (non-blocking): Lines 924–926 emit two consecutive banner echoes before the build ("Building custom images" then "Building disinto/agents:latest"). Redundant but harmless.
Verdict
APPROVE — Build step correctly placed before deploy loop, service detection pattern matches existing convention, docker build failure propagates under pipefail
Reviewed at
0c767d9| AGENTS.mdAI Review: APPROVE — Build step correctly placed before deploy loop, service detection pattern matches existing convention, docker build failure propagates under pipefail