The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

BlazeMeter plugin

blazeMeterTest: BlazeMeter

  • credentialsId (optional)
    Select the BlazeMeter credentials to use.
    • Type: String
  • workspaceId (optional)
    • Type: String
  • testId (optional)
    BlazeMeter's plugin for Jenkins allows users to automate load tests from the cloud post build.
    Just choose the test you want to run. Let Jenkins start and stop the test and document the results.
    After the run, a test report will be generated directly into Jenkins and your BlazeMeter account.
    If the test list is empty, you must insert your unique BlazeMeter API key into the Jenkins settings, or create a test in your BlazeMeter account.
    • Type: String
  • additionalTestFiles (optional)
    Before the test runs these files will be pushed to the selected BlazeMeter test. Existing files with the same name will be replaced. Provide a list of files that are locate in job workspace(relative path, each file on a new line).
    Limitations: Supported test types: Taurus, FunctionalApi, JMeter
    • Type: String
  • getJtl (optional)
    Check this box if you need to download JTL report after test will be over.
    • Type: boolean
  • getJunit (optional)
    Check this box if you need to download junit report after test will be over.
    • Type: boolean
  • jobApiKey (optional)
    • Type: String
  • jtlPath (optional)
    Here you can define desired location for downloading jtl artifact.
    Plugin supports both absolute and relative paths.
    Jenkins environment variables will be resolved.
    • Type: String
  • junitPath (optional)
    Here you can define desired location for downloading junit artifact.
    Plugin supports both absolute and relative paths.
    Jenkins environment variables will be resolved.
    • Type: String
  • mainTestFile (optional)
    Before the test runs this file will be pushed to the selected BlazeMeter test and select as executable file. Existing file with the same name will be replaced. Provide a file that is locate in job workspace(relative path).
    Limitations: For Taurus and FunctionalApi tests will set 'Test type': JMeter if file has '.jmx' extension and Taurus - for '.yml' and '.yaml' files. Other 'Test types', please, set in the BlazeMeter application. Supported test types: Taurus, FunctionalApi, JMeter
    • Type: String
  • notes (optional)
    Enter here some notes that you want to attached to test report.
    • Type: String
  • reportLinkName (optional)
    Report link name that you will see in your build. By default it'll set: "BlazeMeter report: BLAZEMETER_TEST_NAME", where BLAZEMETER_TEST_NAME is a test name from app. By default max report link name length = 35, but you can increase this value using Java System property or Jenkins environment variable "bzm.reportLinkName.length"
    • Type: String
  • serverUrl (optional)
    • Type: String
  • sessionProperties (optional)
    Define jmeter properties for particular session in format key1=value1,key2=value2,key3=value3.
    Properties will be pushed to every separate session of master session.
    • Type: String

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.