Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup

Version History

version 2.8

  •  Fixed a NullPointerException while using "IncludeURLs" in advanced section

version 2.7

  •  Fixed Jenkins required core
  •  Removed unnecessary dependency

version 2.6

  •  Fixed pipeline support and added respective how-to at the bottom of this page

Project Description

The purpose of this plugin is to allow Jenkins to perform dynamic analysis with IBM AppScan Standard with minimal configuration.


First you must set that machine as a node (slave), you can follow this guide to do so.

Afterwards you can use the Node and Label Parameter Plugin, following the guide provided in its wiki achieving this goal should be straightforward.


If you change the CSS options, they won't be applied to the current report, you must re-run the build/scan.


Running AppScan Standard in a Pipeline


The end result would look like the image below.


A resulting script looks something like the one below, you can use this one as your starting point.

stage ('Run AppScan Standard') {
    node {
        step([$class: 'AppScanStandardBuilder', additionalCommands: '', authScanPw: '',
             authScanUser: '', includeURLS: '', installation: 'AppScan Standard Default',
             pathRecordedLoginSequence: '', policyFile: '', reportName: '', startingURL: ''])



Scheduled Tasks for version 2.9

  • Implement Quality Gate support for AppScan Standard (fails build on % of errors)


This version of the plugin was tested with Version 2.8 of this plugin is compatible with:

  • Jenkins 2.0


  • and newer
  • IBM Security AppScan Standard 9.0.3.



version 2.6

  • Fixed pipeline support.



  • Create an option that enables/disables AppScan Standard feed from Jenkins log.
  • Display a message if AppScan Standard installation can't be found.
  • x