Building the project and reviewing its output

This topic describes how:

Before you begin

Perform the procedures in the following topics:

To build a project

Use the following procedure to build a project:

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

To review the console output for a build

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

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

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 path 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 path 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

We recommend 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

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:

From the Dashboard in the Jenkins web user interface, select the project.
Click Workspace.
Select the item corresponding to your build output. The name of the item has the following format:
projectName-buildNumber-jobName-jobID

Schema Change Migration build step results

The following table lists the possible result outcomes of the Schema Change Migration build step.

Return Code	Result
0000/0004	All process steps completed successfully and changes detected in Compare
0001	No changes detected in Compare
0008	Invalid input values may have been encountered in a process step causing the Schema Change Migration build step to fail Analysis may have encountered an error based upon schema definition or utilities selection
0012	SQL error is encountered in a process step causing the Schema Change Migration build step to fail

Schema Standards analysis results

The following table lists the possible result outcomes of a Schema Standards analysis.

Return Code	Result
0000	No violations encountered
0004	Unsupported objects encountered Violations encountered and log mode = WARN Violations encountered and violation was set to ignore
0008	Violations logged Host variable error logged
0012	Invalid input encountered SQL error logged

Host variable and SQL errors are reported for the affected rule in the Schema Standards report (AS$RSLT DD) and logged in the Schema Standards Violation details view. When these errors are received, correct the rule definition in BMC AMI Command Center for Db2.