Skip to content

Implement local Apify actor runtime (POCv2) #13

Implement local Apify actor runtime (POCv2)

Implement local Apify actor runtime (POCv2) #13

Workflow file for this run

name: CI
on:
push:
branches: [master, v2-poc-requirements]
pull_request:
jobs:
checks:
name: Build, lint, unit + integration tests
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 24
cache: npm
- run: npm ci
- run: npm run build
- run: npm run lint
- run: npm run format:check
- run: npm test
e2e:
name: Actor dev-loop e2e (apify-cli + Docker)
runs-on: ubuntu-latest
timeout-minutes: 30
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 24
cache: npm
- run: npm ci
# The suite manages Docker itself against the runner's daemon: it pre-pulls the
# Actor base images, builds the runtime image, starts the runtime container with
# the host Docker socket, and drives it with stock apify-cli via npx.
- run: npm run test:e2e
# The e2e's runtime container is normally removed by the suite's afterAll; on
# failure it is left running, so its server-side view of any failed request
# (log-stream lifecycle included) is captured here for diagnosis.
- name: Dump runtime container logs on failure
if: failure()
run: docker logs actor-runtime-e2e --tail 300 || true