This commit is contained in:
2026-09-24 18:50:08 -03:00
parent 4417645639
commit f7bcad0b38
3 changed files with 69 additions and 20 deletions
+11 -8
View File
@@ -16,16 +16,19 @@ remote Docker daemon. No external registry is required.
./scripts/build-and-push.sh --remote deploy@prod.example.com
```
The script reads `artifactId` and `version` from `pom.xml` for the image name
and version tag, builds for `linux/amd64`, and verifies the image is present on
the remote after pushing. On the remote (and locally) that push is tagged three
ways, all pointing at the same image:
The script reads `artifactId` and `version` from `pom.xml` for the local build tag
and image name, builds for `linux/amd64`, and verifies the deploy on the remote.
On the remote, durable tags are only:
- `<name>:<version>` — the version from `pom.xml` or `--tag`
- `<name>:latest` — moved to this push on every successful deploy
- `<name>:vYYYY.MM.DD-HH.MM` — UTC timestamp of the push (for rollback; list with `docker images`)
- `<name>:latest` — always the most recent successful push
- `<name>:vYYYY.MM.DD-HH.MM` — UTC timestamp of that push (for rollback)
To roll back on the remote, pick an older `v…` tag from `docker images test-quarkus` and run that reference instead of `:latest`.
Older releases stay tagged by date only: the script keeps the current image (with
`latest` and its date tag) and the previous date tag, and removes other tags and
images (including old `1.0.x`, `sha256-*`, and third copies). Run
`--cleanup` on the remote to apply the same pruning without a new push.
To roll back on the remote, run a previous `v…` tag from `docker images` instead of `:latest`.
The temporary registry container and SSH tunnel are removed when the script
finishes. See `./scripts/build-and-push.sh --help` for all flags.