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.

Defensics

View this plugin on the Plugins site

defensics: Defensics fuzz test

  • configurationFilePath : String

    The file path where the test configuration file (*.set or *.testplan) for this job can be found, relative to the project's workspace.

    A test configuration file defines what kind of testing is to be done, and can be created using Defensics. Configure a test suite in Defensics and save the settings file in File -> Save Settings.

  • configurationOverrides : String (optional)

    Additional test configuration settings that override the settings saved in the test configuration file. This can be useful if, for example, the test target address needs to be set dynamically.

    The available settings are the same as the Defensics command line settings. Each setting should follow the format '--setting-name value'. Multiple settings are separated with spaces.

    Example for HTTP Server Test Suite:

    --uri https://example.com --http-status-filter "1xx 2xx 3xx"

  • defensicsInstance : String (optional)
    Select Defensics instance to use for running tests. Instances can be added in Jenkins' global configuration under the Defensics section.
  • saveResultPackage : boolean (optional)
    Check this if you want Jenkins to download the Defensics result package and store it for the build. The result package includes all logs for the test run. The package can be downloaded from the build status page. Use with caution as the package filesize can be large.

step([$class: 'FuzzBuildStep']): Defensics fuzz test

  • configurationFilePath : String

    The file path where the test configuration file (*.set or *.testplan) for this job can be found, relative to the project's workspace.

    A test configuration file defines what kind of testing is to be done, and can be created using Defensics. Configure a test suite in Defensics and save the settings file in File -> Save Settings.

  • configurationOverrides : String (optional)

    Additional test configuration settings that override the settings saved in the test configuration file. This can be useful if, for example, the test target address needs to be set dynamically.

    The available settings are the same as the Defensics command line settings. Each setting should follow the format '--setting-name value'. Multiple settings are separated with spaces.

    Example for HTTP Server Test Suite:

    --uri https://example.com --http-status-filter "1xx 2xx 3xx"

  • defensicsInstance : String (optional)
    Select Defensics instance to use for running tests. Instances can be added in Jenkins' global configuration under the Defensics section.
  • saveResultPackage : boolean (optional)
    Check this if you want Jenkins to download the Defensics result package and store it for the build. The result package includes all logs for the test run. The package can be downloaded from the build status page. Use with caution as the package filesize can be large.

step([$class: 'FuzzPostBuildStep']): Defensics fuzz test

  • configurationFilePath : String

    The file path where the test configuration file (*.set or *.testplan) for this job can be found, relative to the project's workspace.

    A test configuration file defines what kind of testing is to be done, and can be created using Defensics. Configure a test suite in Defensics and save the settings file in File -> Save Settings.

  • configurationOverrides : String (optional)

    Additional test configuration settings that override the settings saved in the test configuration file. This can be useful if, for example, the test target address needs to be set dynamically.

    The available settings are the same as the Defensics command line settings. Each setting should follow the format '--setting-name value'. Multiple settings are separated with spaces.

    Example for HTTP Server Test Suite:

    --uri https://example.com --http-status-filter "1xx 2xx 3xx"

  • defensicsInstance : String (optional)
    Select Defensics instance to use for running tests. Instances can be added in Jenkins' global configuration under the Defensics section.
  • saveResultPackage : boolean (optional)
    Check this if you want Jenkins to download the Defensics result package and store it for the build. The result package includes all logs for the test run. The package can be downloaded from the build status page. Use with caution as the package filesize can be large.

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.