Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI SQL Assurance for Db2 13.1.

Building the project and reviewing its output

This topic contains the following sections:

Before you begin

Perform the procedures in the following topics:

How to build a project

Use the following procedure to build a project:

  1. From the Dashboard in the Jenkins web user interface, select the project that you want to build.
  2. Click Build with Parameters.
  3. Enter values for the parameters.
    Jenkins schedules a build for your project. 

How to review the console output for a build

Use the following procedure to review the console output after building the project:

  1. From the Dashboard in the Jenkins web user interface, select the project.
  2. From the Build History panel, select your build number.
  3. Click Console Output.
  4. Review the following items from the Console Output section:
    • Job name
    • Return code
    • Number of files

    • Build status

      On evaluation of SQL statements, if you discover violations then the return code and the build status partially depends on the definition of Violation Response in your project.

      Violation Response is the application's reaction when violations are encountered.

      Violation Response

      Description

      Fail

      Fail will cause a rule violation to fail the plugin step. The job will receive Return code 8.

      Warn

      Warn will allow the plugin step to succeed, if a violation is encountered. The job will receive Return code 4. 

      This is common in both BMC AMI SQL Assurance for Db2 - Analyze Static SQL and BMC AMI SQL Assurance for Db2 - Analyze Dynamic SQL plugin steps.


You can also review the console output log for your build from the log file, which is generated on your system at the following paths when you build the project:

Click here if you are using Jenkins on Windows

installationDirectory\Jenkins\jobs\projectName\builds\buildNumber

In this path,

  • The installationDirectory variable represents the directory on your system on which Jenkins is installed.
  • The projectName variable represents the name of the project.
  • The buildNumber variable represents the sequential number that Jenkins has assigned to the project build.

If you have created the project inside a folder, the log file is generated on your system at the following path:

installationDirectory\Jenkins\jobs\folderName\jobs\projectName\builds\buildNumber

In this path, the folderName variable represents the name of the folder inside which the project is created.

Click here if you are using Jenkins on Linux

/installationDirectory/jenkins/jobs/projectName/builds/buildNumber

In this path,

  • The installationDirectory variable represents the directory on your system on which Jenkins is installed.
  • The projectName variable represents the name of the project.
  • The buildNumber variable represents the sequential number that Jenkins has assigned to the project build.

If you have created the project inside a folder, the log file is generated on your system at the following path:

/installationDirectory/Jenkins/jobs/folderName/jobs/projectName/builds/buildNumber

In this path, the folderName variable represents the name of the folder inside which the project is created.

Warning

BMC recommends that you do not use Notepad to review the console output log because Notepad does not display the line feed correctly. You can use any of the following applications:

  • WordPad
  • Microsoft Word (English encoding)
  • NotePad ++
  • SlickEdit

How to review the JES job log output for a build

Use the following procedure to review the JES job log output after building the project:

  1. From the Dashboard in the Jenkins web user interface, select the project.
  2. Click Workspace.

  3. Select the item corresponding to your build output. The name of the item has the following format:

    projectName-buildNumber-jobName-jobID

    SA1-261-COBDSQL-J0157779

  4. Select the SA Violations Report, to view the SQL violations for your build. The name of the item has the following format:

    projectName-buildNumber-Static/Dynamic SQL-jobNumber-SA Violations Report

    SA1-261-Static SQL-J0157779-SA Violations ReportFor more information on SQL Assurance report, see Sample-SQL-Assurance-report-AS-RSLT.

  5. Select the Explain report, to view the Explain analysis for your build. The name of the item has the following format:

    projectName-buildNumber-Static/Dynamic SQL-jobNumber-Explain Report

    SA1-18-Dynamic SQL-J0180603-Explain Report

Related topic

Using-BMC-AMI-SQL-Assurance-in-Jenkins


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*