CI/CD Integration

Run AegisRunner as part of your pipeline. Under Manage → Integrations, create a trigger token for the project.

Triggering from CI

POST to the trigger endpoint with your token to kick off a scan or a test run from GitHub Actions, GitLab CI, Jenkins, CircleCI — anywhere that can make an HTTP request. The run shows up in the Runs lens and Activity panel like any other.

The aegis CLI

Prefer a command line over raw HTTP? Install the aegis CLI (zero dependencies, Node 18+):

npm install -g https://aegisrunner.com/cli/aegisrunner-cli-1.0.0.tgz

Then, with your trigger token in AEGIS_TOKEN:

# run everything, wait, and write a JUnit report for your CI
aegis run --format junit --output aegis-results/junit.xml

# run a smart selection on Firefox
aegis run --strategy smoke --browser firefox

# re-scan the site, or your mobile app, after a deploy
aegis scan --url https://staging.example.com
aegis mobile-scan --platform android --role customer

Exit code 0 means everything passed, 1 means test failures (fails your pipeline step), 2 means the CLI could not complete. The JUnit file contains real per-case rows — point GitLab artifacts: reports: junit: or Jenkins at it.

Results back to your pipeline

Pair triggers with webhook or issue-tracking integrations (GitHub Issues, Jira) so failures land where your team already works. Tokens are scoped per project and can be revoked anytime.