ci: use yarn instead of npm (npm Exit handler bug)
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful

This commit is contained in:
2026-04-11 14:05:24 +05:30
parent 460e422c94
commit f6554b95d4

View File

@@ -1,19 +1,24 @@
# Woodpecker CI pipeline for Helix Engage # Woodpecker CI pipeline for Helix Engage
# #
# Triggered on push or manual run. # Triggered on push or manual run.
# Runs E2E smoke tests against live EC2 deployment.
when: when:
- event: [push, manual] - event: [push, manual]
steps: steps:
typecheck:
image: node:20
commands:
- corepack enable
- yarn install --frozen-lockfile || yarn install
- yarn tsc --noEmit
e2e-tests: e2e-tests:
image: mcr.microsoft.com/playwright:v1.52.0-noble image: mcr.microsoft.com/playwright:v1.52.0-noble
commands: commands:
- node --version - corepack enable
- npm install --registry=https://registry.npmjs.org --ignore-scripts 2>&1 || npm install --registry=https://registry.npmjs.org --ignore-scripts --legacy-peer-deps - yarn install --frozen-lockfile || yarn install
- npx playwright install chromium - npx playwright install chromium
- npx playwright test --reporter=list - npx playwright test --reporter=list
environment: environment:
E2E_BASE_URL: https://ramaiah.engage.healix360.net E2E_BASE_URL: https://ramaiah.engage.healix360.net
NODE_OPTIONS: --max-old-space-size=4096