This commit is contained in:
@@ -10,8 +10,9 @@
|
||||
# This was the build-logic `ca.developer-bootstrap` plugin (`./gradlew bootstrap`). Starting
|
||||
# containers and probing an HTTP endpoint is not a build rule, so it is a script now (review
|
||||
# 2026-09-24 BUILD-O3-5). The four stages and their order are unchanged: the next stage starts only
|
||||
# when the previous one succeeded, and the app stage waits for startup Flyway through the compose
|
||||
# healthcheck before the smoke probe runs.
|
||||
# when the previous one succeeded, and the app stage waits for the compose healthcheck before the
|
||||
# smoke probe runs. The default composition is web only: it opens no datasource and runs no
|
||||
# Flyway. A service that adds the persistence-jpa line gets startup Flyway inside the same wait.
|
||||
#
|
||||
# Until 2026-11-07 it merged docker-compose.yml with docker-compose.local.yml and asked for a `db`
|
||||
# service neither file had defined since the database moved to a third file, so the documented
|
||||
@@ -40,7 +41,7 @@ fi
|
||||
echo "bootstrap 2/4: starting the PostgreSQL dependency and waiting for readiness"
|
||||
"${compose[@]}" up -d --wait db
|
||||
|
||||
echo "bootstrap 3/4: building and starting the app; startup Flyway finishes before health is ready"
|
||||
echo "bootstrap 3/4: building and starting the app and waiting for its health"
|
||||
"${compose[@]}" up -d --build --wait app
|
||||
|
||||
echo "bootstrap 4/4: requiring HTTP 200 and status=UP from ${health_endpoint}"
|
||||
|
||||
Reference in New Issue
Block a user