Versions Compared

Key

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

...

  1. From the Jenkins homepage, click Manage Jenkins and then Global Tool Configuration
  2. Scroll down the page and locate the section titled AppScan Standard
  3. Click Add AppScan Source
  4. Fill out the AppScan Source form
    ## Name: A name for this instance of AppScan Standard. This is just to help manage environments that may have multiple installations
    1. AppScan Standard Installation Directory: The path to the installation directory. Note: the default value is C:\Program Files (x86)\IBM\AppScanStandard
  5. Click Save

...

  1. Create a new job or access an existing job
  2. Select "Configure"
  3. Select "Add build step" and select "Run AppScan SourceStandard"
  4. Complete the fields that appear:
    1. AppScan Source Standard installation will show the name you provided for the installation on the global configuration screen. If
      1.  If you have not added an installation, please go the the Jenkins
      Configure System
      1. Global Tool Configuration link under Manage Jenkins.
      If
      1.  If you only have one installation configured, the installation should be selected for you. If you plan to execute AppScan
      Source
      1. Standard on multiple Jenkins nodes, you may need to configure multiple installation paths.
    2. Disable scan should be unchecked if you wish the scan to run
    3. Accept SSL Errors should be checked if you have not created a trusted certificate for your AppScan Source installation. In an Enterprise environment, this should not be checked, since you should be using a trusted certificate.
    4. Scan Workspace Directory is where scan artifacts, like WAFL and staging files will be placed. Scan results (.ozasmt file) will also be placed in this directory.
    5. Application file should point to a PAF or SLN file to scan.
    6.  
  5. Click Save at the bottom
  6. Run the job.

...