actions-marketplace-validations/taurus-action

Run a taurus performance test

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/rbillon59_taurus-action@c48fb5381ce419d2d29e1ebdfe98543aed3a17e9 # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
taurus_project_folder_name	The name of the folder containing the taurus scenario and datas. \ The repo architecture should be like this : \ +-- repo_code \ +-- my-scenario \ +-- dataset.csv \ +-- my-scenario.yaml	yes	—
taurus_command_line	The taurus command line arguments to execute. Basically contains the yaml testfile to execute. More info here https://gettaurus.org/docs/Index/ \ The container entrypoint is the "bzt" command without any arguments \ The simpler case would be : \ my-scenario.yaml \ from the above file structure example, which will execute bzt my-scenario.yaml inside the container	yes	—
blazemeter_api_token	If you want to upload report to blazemeter you can set your API token here. \ It will appen the command line with : \ -o modules.blazemeter.token=${blazemeter-api-token} \ You can still use the -report inside the command line input to upload results as anonymous to Blazemeter	no	—

name	description
exit-code	Taurus exit code : \ 0 — No problems occured. \ 1 — Taurus finished with a generic error (networking, internal Taurus errors) \ 2 — Taurus was manually shut down (Ctrl-C by user, process received SIGKILL, etc) \ 3 — Taurus was shut down automatically (e.g. Pass/Fail criteria, cloud tests failed, etc)