The base-node-deps Docker build failed because .npmrc routes @esbuild-kit
packages to localhost:4873 (Verdaccio), which is unreachable inside BuildKit.
- Add Verdaccio service to docker-compose.stack.yml with patched tarballs
- Start Verdaccio in Gate 7 Tier 1 before base-node-deps build
- Configure buildx with network=host so BuildKit can reach localhost:4873
- Update verdaccio.yaml storage path for container volume mount
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Move Gate 7 container builds (base images T1→T2→T3 + app images) to
run right after Gate 1 instead of after Gate 3. Gate 2 (E2E) now
depends on container-build-apps completing, so the smoke stack pulls
prod images from GHCR — no special E2E images, same images used
everywhere.
- container-base-tier1 needs gate-1-complete (was gate-3-complete)
- container-build-apps runs on all events including PRs
- All images push: true unconditionally (E2E needs them in GHCR)
- E2E just logs into GHCR, smoke compose pulls via image: directives
- Added dbal + dbal-init to Gate 7 app matrix
https://claude.ai/code/session_01ChKf8wbKQLBcNbBCtqCwT6
Replace manual docker compose start/stop in the CI workflow with
Testcontainers in Playwright global setup/teardown. This gives:
- Automatic container lifecycle tied to the test run
- Health-check-based wait strategies per service
- Clean teardown even on test failures
- No CI workflow coupling to Docker orchestration
Changes:
- e2e/global.setup.ts: Start smoke stack via DockerComposeEnvironment
(nginx, phpMyAdmin, Mongo Express, RedisInsight) with health check waits
- e2e/global.teardown.ts: New file — stops Testcontainers environment
- e2e/playwright.config.ts: Register globalSetup/globalTeardown, bind dev
servers to 0.0.0.0 in CI so nginx can proxy via host.docker.internal
- gated-pipeline.yml: Remove docker compose start/stop/verify steps,
add 10min timeout to Playwright step
- e2e/deployment-smoke.spec.ts: Update doc comment
- package.json: Add testcontainers@^11.12.0 devDependency
https://claude.ai/code/session_018rmhuicK7L7jV2YBJDXiQz
The compact formatter was removed from ESLint core. Switch to the
default stylish formatter and adjust the error-counting grep pattern.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
All 13 occurrences of || true removed — test failures (playwright,
vitest, eslint, builds) now exit non-zero and fail the job/workflow.
Added set -o pipefail to the eslint and vitest steps so pipe-through-tee
doesn't swallow the test runner exit code.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- deployment/docker-compose.smoke.yml: stock-image stack (nginx stub
gateway + real phpMyAdmin/Mongo Express/RedisInsight + their DB deps)
using tmpfs for ephemeral infra — no custom image builds required
- deployment/config/nginx-smoke/default.conf: stub nginx returns 200
for all app paths and "MetaBuilder" on root for portal test
- Gate 2.2: starts smoke stack before playwright (--wait, 3 min
timeout) and tears it down after with -v to clean volumes
- e2e/playwright.config.ts: removed testIgnore — all tests run
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Create a CI user on Verdaccio via CouchDB API and set _authToken before
publishing patched tarballs (fixes ENEEDAUTH)
- Retry npm install up to 3 times with 15s delay for transient ECONNRESET
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add webServer config to e2e/playwright.config.ts: starts Next.js workflowui
on port 3000 automatically when PLAYWRIGHT_BASE_URL is not set
- Default baseURL changed to http://localhost:3000/workflowui/ (Next.js dev)
- Override via PLAYWRIGHT_BASE_URL=http://localhost/workflowui/ for Docker stack
- Add workspace build step before playwright in Gate 2.2 (packages needed by workflowui)
- Fix playwright-report upload path (was frontends/nextjs/playwright-report/)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Nexus takes 5+ minutes cold-start; Verdaccio starts in ~2 seconds.
Verdaccio serves patched packages and proxies everything else to npmjs.org.
Nexus remains the local dev registry for Docker images and Conan packages.
- Replace composite action Nexus startup with Verdaccio (npx verdaccio)
- Update @esbuild-kit:registry in .npmrc from :8091/repository/npm-group/ to :4873
- Update publish-npm-patches.sh to support --verdaccio / --nexus flags with
auto-detection (checks Nexus first, falls back to Verdaccio)
- Add deployment/verdaccio.yaml config for local dev use
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Remove stale dirs/files superseded by metabuilder-small's reorganization:
- Old YAML entity/seed files (migrated to JSON)
- Root-level workflowui/ (moved to frontends/workflowui/)
- Prisma, Pyodide, old hooks, bun.lock artifacts
- Legacy scratch docs (txt/, docs/, deployment/*.md)
- Stale CI workflows consolidated in small
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Use 'prisma/config' import (re-export from @prisma/config for better compatibility)
- Change workflow condition from always() to failure() for proper job triggering
- Fix migration rollback command syntax with proper schema path
- All changes verified and tested successfully
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Rename rollback-preparation job to deployment-failure-handler
- Add detection of pre-deployment vs production failures
- Provide clear roll-forward guidance emphasizing it as preferred approach
- Include when rollback is appropriate (only for critical production issues)
- Create more actionable issues with fix-forward checklists
- Add helpful troubleshooting for common pre-deployment failures
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
Enhancement based on user feedback:
- Create gated-ci-atomic.yml with 12 atomic validation steps
- Each validation tool from /tools runs as separate job
- Gate artifacts persisted via GitHub Actions artifacts (30-day retention)
- Superior visualization: each step shows individual status
- Complete audit trail with JSON artifacts for compliance
- Leverages existing atomic tools: security-scanner, file-size checker, complexity analyzer, stub detector, etc.
- Add comprehensive atomic workflow documentation (11KB)
- Update workflows README with atomic workflow section
Benefits:
- Granular failure detection (know exactly which validation failed)
- Parallel execution within gates
- Individual step timing and artifact preservation
- Better for large teams and enterprise compliance
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
