8.4 Release and Deployment Quick Reference

Type: Reference page, no required sequential reading Prerequisites: Full lifecycle and CI/CD You are ready to continue when: you can quickly locate artifacts, versions, deployments, and rollback evidence

End-to-End Quick Reference

Stage	Typical Actions	Mandatory Evidence
Integration	checkout, compile, test, verify	commit SHA, test results
Packaging	Maven package / verify	JAR, hash, build log
Image build	docker build	image ID, base image, SBOM
Release	push artifact/image	registry digest, provenance
Deployment	update target declaration	environment, time, operator, old/new digest
Traffic rollout	health, smoke, gradual traffic increase	metrics, logs, error budget
Rollback	restore known good version	trigger conditions, target digest, verification results

Local Check

mvn --batch-mode verify
sha256sum target/*.jar
docker image inspect name:tag
docker container inspect name
docker logs --tail 100 name

These snippets target existing projects and containers; replace name:tag and name. When multiple JARs match a wildcard, explicitly select the primary artifact. The macOS hash command is available at shasum -a 256.

Registry Template

printf '%s' "$REGISTRY_TOKEN" | docker login REGISTRY \
  --username "$REGISTRY_USER" --password-stdin
docker tag local:candidate registry.example.com/owner/image:sha-COMMIT
docker push registry.example.com/owner/image:sha-COMMIT
docker logout REGISTRY

REGISTRY, the user variable, commit marker, and registry.example.com/owner/image are placeholders. The login host must match the push target, and image repository paths use lowercase. Inject variables only in controlled terminals or CI environments. Do not write real tokens into the repository, command examples, or shell history. Deployment records use the digest returned by push, rather than movable tags alone.

Pre-Release Check

• [ ] Testing, static analysis, and vulnerability strategies have passed;
• [ ] Candidate artifacts are built only once, and their hashes and digests are recorded;
• [ ] Configurations and secrets belong to the correct environment;
• [ ] Database migrations are compatible with rollbacks;
• [ ] Health, smoke, metrics, and log queries are prepared;
• [ ] Known good versions and rollback permissions are available;
• [ ] Concurrency deployment and manual gate strategies are clearly defined.

Common Errors

Error	Check First
Address already in use	Host listening and container port publishing
no main manifest attribute	JAR manifest, main class, and repackage configuration
registry denied	Repository name, login credentials, token scope, and package access relationships
Deployment still serves the old version	Actual digest, container image ID, proxy and browser caching
Rollback still fails	Database/configuration compatibility, external dependencies, and caching and traffic routing