Repository navigation
Deploy script: recreate the build agent when its image changed - #115
Merged
Merged
Conversation
A deploy that rebuilt the agent's image left the runner on the old one: `compose up -d` reported the containers as Running and recreated nothing, so the check after it failed - and deploying again would do the same. The script already knows the image changed when it gets there, so the recreate is forced. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A deploy that rebuilt
genhttp-agent:latestended withThe check was right: the script had found the runner's image to differ from the one just built, yet
docker compose up -d agent egress-proxydid not recreate the containers - compose does not reliably notice an image built by an earlier, separatecompose build. Deploying again, as the message advises, would rebuild from cache and hit the same no-op.The recreate is now
--force-recreate. It is only reached once the image is known to have changed and the running builds have finished, so a deploy where the agent did not change still recreates nothing.To bring the server in line now:
up -d --force-recreate agent egress-proxywith the three compose files (nobuild-*containers running), thengenhttp-deploy --check.🤖 Generated with Claude Code