Skip to content

JMeter CLI Command Builder

Build a JMeter CLI command: non-GUI run, JTL results, HTML dashboard, HEAP, -J properties, and GitHub Actions or Docker snippets.

Difficulty
beginner
Guide type
how-to
Estimated read time
3 min read
Last verified version
Verified JMeter 5.6

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.

    FlagPurpose
    -nNon-GUI (CLI) mode — required for real load
    -tTest plan (.jmx)
    -lResults file (.jtl / CSV)
    -e -oGenerate the HTML dashboard into an empty folder
    -fOverwrite existing results and report directory
    -qExtra properties file (prefer this over editing jmeter.properties)
    -jJMeter log file
    -Jname=valueSet a property for this run (__P in the plan)
    -RRemote worker hosts (start jmeter-server first)
    -XExit 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.

    1. Size threads and think time with the Thread Calculator.
    2. Build the CLI command here (add -e -o for a dashboard artifact).
    3. Parameterize hosts and threads with -J / __P so the same .jmx works in every environment.
    4. Gate the pipeline on dashboard error rate and percentiles, not only the process exit code.
    On this page