Node.js web release
✓ EXAMPLE RUNInstall, verify and package a Node.js application. This public run is an example of the output your workspace keeps.
EXAMPLE PIPELINEweb-console / main#1482
01 / SOURCEcheckout✓ 4 sec
02 / VERIFYlint + typecheck✓ 18 sec
03 / VERIFYunit tests✓ 32 sec · 186 tests
04 / COMPILEbuild release✓ 48 sec · cache hit
05 / DELIVERartifacts↓ app.tar.gz · 38 MB
00:00.00 Provisioning linux-x64 / 4 vCPU / 8 GB
00:03.82 Repository checked out at 7a91c2e
00:04.10 Restoring content-addressed dependency cache
00:06.42 CACHE HIT · 214 MB restored
00:07.01 Running verification stages in parallel
00:39.36 186 tests passed · 0 failed
00:40.01 Compiling production release
01:21.10 Packaging output and test reports
01:24.00 Build succeeded. 3 artifacts available.
name: web-release
runner: linux-x64-4
steps:
- run: pnpm install --frozen-lockfile
cache: node_modules
- parallel:
- run: pnpm lint && pnpm typecheck
- run: pnpm test --reporter=junit
- run: pnpm build
artifacts:
paths: [dist/**, junit.xml, sourcemaps/**]
retention: 14dapp.tar.gzProduction bundle
38 MBjunit.xmlJUnit test report
84 KBsourcemaps.zipSource maps
16 MBArtifact downloads require membership in the source workspace.
Sign in to retrieve artifacts ↗BEFORE YOUR FIRST RUN
A small config.
A complete build.
Save your pipeline as .runway.yml in the repository root. Each job gets a clean workspace. Only declared caches and artifacts survive a run.
Runner requirements
- Source
- Git repository over HTTPS
- Secrets
- Workspace-scoped environment variables
- Job timeout
- 60 minutes by default
- Maximum artifact
- 5 GB per file on Team
- Download format
- Original file or ZIP archive