ci: run the database tests against postgres #277
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-web!277
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "ci/postgres-tests"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
What
Run the database-backed tests in CI.
scripts/purge-expired.db.test.mjs(GDPR purge, #275) skipped there because CI had no Postgres.postgres:17withpodman run -p 5432:5432and waits onpg_isready. It is a step, notservices:: thecirunner is a host executor and never starts service containers.node scripts/migrate.mjs.DATABASE_URLis set on that step only, so build and e2e still run without a database.TEST_DATABASE_URLis set for the job. The DB test file now throws whenCIis set without it, so it can never skip silently again.Verification
Local, postgres:17 with migrations applied,
CI=trueandTEST_DATABASE_URLset: 35/35 files, 492/492 tests, 0 skipped.CI=truewithout the variable: the DB test file fails. This PR's own CI run proves the step on the runner.