chordpli/tmula run
Run a tmula traffic scenario against your service and gate CI on what broke: journey regressions, contract violations, availability dips. Optionally diff against a baseline run so only new findings fail the job. The run summary lands on the workflow page, and optionally as a PR comment.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 16, 2026
- License
- Apache 2.0
Pinned Snippet
uses: chordpli/tmula@d3256d74e558b9e0739d88efeedce04a19c7454c # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| scenario | Path to the scenario file (YAML/JSON). Omit only if extra-args supplies a single-endpoint probe. | no | "" |
| target | Target base URL; overrides the scenario file's target. | no | "" |
| users | Closed-model virtual user count. | no | "" |
| open | Open model arrivals per second. | no | "" |
| for | Open model duration in seconds. | no | "" |
| fail-on | Gate: 'findings' fails on any finding, 'warning'/'critical' on that severity and above, 'none' never fails. | no | findings |
| baseline-file | Path to a baseline report JSON (a previous `tmula run --json` output, e.g. an artifact saved by the main-branch run). Turns on the regression gate: the run fails only on findings new vs the baseline (exit 3), so known problems do not block every PR. Combine with `fail-on: none` to gate purely on regressions. | no | "" |
| known-issues | Path to a known-issues YAML; matching new findings are suppressed in the baseline gate until their expires date. Only valid with baseline-file. | no | "" |
| version | tmula release tag to install (default latest). Pin this for reproducible runs. | no | "" |
| comment | Post the run summary as a PR comment (needs the workflow's pull-requests write permission). | no | false |
| pr-comment | Post the baseline gate verdict (the new / resolved / persisting / suppressed table) as a PR comment, editing the same comment in place on re-runs instead of stacking new ones like `comment` does. Without a baseline it posts the full run summary. Needs the workflow's pull-requests write permission; fork PRs get a read-only token, so the comment is skipped with a warning there. | no | false |
| extra-args | Extra raw arguments appended to `tmula run`. | no | "" |
Outputs
no outputs