Author SHA1 Message Date
james.maes fb255928b7 Merge pull request 'ci: verify on the shared ci-workflows Maven workflow' (#8) from ci/ci-workflows into main
maven / build (push) Successful in 52s
build / maven (push) Successful in 52s
2026-11-07 20:07:57 +00:00
James MaesandClaude Opus 5.5 61aa6f64c0 build(db): bump Testcontainers to 1.21.4
maven / build (push) Successful in 1m33s
build / maven (push) Successful in 1m33s
1.20.1 cannot talk to the CI runners' current Docker Engine (it pins an
API version the daemon no longer accepts), so the migration ITs failed
with "Could not find a valid Docker environment". 1.21.4 negotiates a
supported API version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 14:05:53 -06:00
James MaesandClaude Opus 5.5 d95240e34f ci: verify on the shared ci-workflows Maven workflow
maven / build (push) Failing after 1m54s
build / maven (push) Failing after 1m54s
Replace the GitHub workflows that called the retired qqq-orb
(business-e2e, business-db) with KofTwentyTwo/ci-workflows
maven.yaml@v1, verify only (publish: false). Every push runs mvn verify,
which includes the db module's empty-database migration tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-07 14:01:57 -06:00
james.maesandCodex 94f5031d94 fix: restore shared live-service e2e validation (#5)
Co-authored-by: Codex <noreply@openai.com>
2026-10-21 01:46:43 -05:00
5 changed files with 12 additions and 34 deletions

No files matched your search

+10
View File
@@ -0,0 +1,10 @@
name: build
on:
push:
jobs:
maven:
uses: self:KofTwentyTwo/ci-workflows/.gitea/workflows/maven.yaml@v1
secrets: inherit
with:
# Application: verify every push (unit, db migration and Testcontainers tests); no artifact publish.
publish: false
-15
View File
@@ -1,15 +0,0 @@
name: Database migrations
'on':
pull_request: {}
push:
branches:
- main
permissions:
contents: read
jobs:
validate:
uses: QRun-IO/qqq-orb/.github/workflows/business-db.yml@0f33ddadf88b9a1b940b8883782fe2000ee1d2bd
concurrency:
group: business-db-${{ github.workflow }}-${{ github.event.pull_request.number ||
github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
-17
View File
@@ -1,17 +0,0 @@
name: Required E2E validation
'on':
pull_request: null
push:
branches:
- main
workflow_dispatch: null
permissions:
contents: read
concurrency:
group: e2e-${{ github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
validate:
uses: QRun-IO/qqq-orb/.github/workflows/business-e2e.yml@0f33ddadf88b9a1b940b8883782fe2000ee1d2bd
secrets:
E2E_ALERT_WEBHOOK_URL: ${{ secrets.E2E_ALERT_WEBHOOK_URL }}
+1 -1
View File
@@ -12,7 +12,7 @@
<name>Platform Database Migrations</name>
<properties>
<testcontainers.version>1.20.1</testcontainers.version>
<testcontainers.version>1.21.4</testcontainers.version>
</properties>
<dependencies>
+1 -1
View File
@@ -27,7 +27,7 @@ Requires Keycloak on `localhost:18081` and the platform API on `localhost:18080`
- `npm run test:e2e` runs Playwright against the real API and Keycloak services; it never mocks them. Playwright starts the frontend on port 3004 when needed.
- `npm run build` automatically runs type checks, unit tests, and the complete E2E suite first. A failed or unavailable live service blocks the build.
- `npm install`/`npm ci` enables the repository pre-commit hook. Commits touching platform code, infrastructure, tests, or workflows run the E2E suite and are rejected on failure.
- `.github/workflows/e2e.yml` starts the actual Compose services on every pull request, main push, nightly schedule, and manual dispatch. Its `Deployment gate / E2E passed` status cannot succeed when E2E fails.
- CI is `.gitea/workflows/build.yaml` (shared `KofTwentyTwo/ci-workflows` Maven workflow): `mvn verify` on every push, including the empty-database migration tests. The live-service Compose E2E job ran through the retired GitHub qqq-orb workflow and is not ported to Gitea yet; run `npm run test:e2e` against the live stack locally (the pre-commit hook enforces it).
- HTML, JUnit, traces, screenshots, and videos are retained as workflow artifacts. Failures appear in the Actions summary and can be sent to a JSON incoming webhook (including Slack-compatible receivers) by defining the `E2E_ALERT_WEBHOOK_URL` Actions secret.
Repository administrators should make **Required E2E validation / E2E / live services** and **Deployment gate / E2E passed** required branch-protection checks. Deployment workflows must depend on the deployment-gate job (or this workflow's successful conclusion); do not permit manual success overrides.