Build a JMeter CLI command: non-GUI run, JTL results, HTML dashboard, HEAP, -J properties, and GitHub Actions or Docker snippets.
JMeter CLI Command Builder
Section titled “JMeter CLI Command Builder”Assemble a non-GUI JMeter command you can paste into a terminal, GitHub Actions, or Docker. Paths stay in your browser; nothing is uploaded.
Assembles flags only. Paths stay in your shell; nothing is uploaded. See CI/CD load testing and Best Practices.
What the flags mean
Section titled “What the flags mean”| Flag | Purpose |
|---|---|
-n | Non-GUI (CLI) mode — required for real load |
-t | Test plan (.jmx) |
-l | Results file (.jtl / CSV) |
-e -o | Generate the HTML dashboard into an empty folder |
-f | Overwrite existing results and report directory |
-q | Extra properties file (prefer this over editing jmeter.properties) |
-j | JMeter log file |
-Jname=value | Set a property for this run (__P in the plan) |
-R | Remote worker hosts (start jmeter-server first) |
-X | Exit remote servers when the test ends |
HEAP is an environment variable consumed by JMeter startup scripts, not a jmeter flag. Size it with the Heap Estimator.
Typical workflow
Section titled “Typical workflow”- Size threads and think time with the Thread Calculator.
- Build the CLI command here (add
-e -ofor a dashboard artifact). - Parameterize hosts and threads with
-J/__Pso the same.jmxworks in every environment. - Gate the pipeline on dashboard error rate and percentiles, not only the process exit code.