Artillery GitHub Action

Official GitHub Action for running load tests with Artillery.

Versioning

Starting with v2.0.30, this action's version tracks the version of the Artillery CLI it wraps. For example, artilleryio/action-cli@v2.0.30 runs Artillery 2.0.30.

Supported tag forms:

• @v2.0.30 — pinned to an exact Artillery version (recommended for reproducible runs).
• @v2 — latest release for Artillery 2.x.

Prebuilt image

The action runs a prebuilt Docker image published to GitHub Container Registry at ghcr.io/artilleryio/action-cli. This avoids rebuilding the image (including Playwright + Chromium) on every job run, so consumers see much faster startup times. Only linux/amd64 is published.

Inputs

command

The Artillery CLI command to run. You can use all the available commands:

• run
• run-fargate
• run-lambda

- name: Load tests
  uses: artilleryio/action-cli@v1
  with:
    command: run ./preprod.yml

Learn more about Writing test scripts with Artillery.

working-directory

• Optional

Path to a directory to use as the current working directory when running Artillery commands.

- name: Load tests
  uses: artilleryio/action-cli@v1
  with:
    command: run ./test.yml
    working-directory: ./packages/app/load-tests

Outputs

This action does not set any outputs.

You can generate and access the test run report using the CLI directly:

- name: Load tests
  uses: artilleryio/action-cli@v1
  with:
    # Save the test run report at "./report.json"
    command: run ./prod.yml --output ./report.json

- name: Upload artifact
  uses: actions/upload-artifact@v3
  if: always()
  with:
    name: artillery-report
    # Reference the generated report in the file system.
    path: ./report.json

Usage examples

Learn more about Running Artillery on GitHub Actions.

Bugs / Questions

Talk to us in the main artilleryio/artillery repo

• Issues
• Discussions