Builds page

The Builds page shows:

  • Running and completed builds

  • Status for each build (such as successful or ended because of an error)

  • Additional build information

Functionality

  • Click a build name to open that build’s Build Details page, which provides detailed information about the build, including access to the Build Log.

To configure the Builds page so that users can see only their own builds, see the Permissions topic.
  • After filtering builds , you can then stop or delete the builds in the filtered results by clicking the or button respectively

  • The Actions column lets you delete or stop a build or view its build-related messages by clicking the or button respectively

  • You can also:

  • Click a column heading to sort the information in that column

  • Set the page refresh interval to keep the information current

  • Set the number of records you want to see per page

Column Descriptions

ColumnDescription

ID

Build ID number assigned by the Cluster Manager

Name

Build name as defined by the build class tag definition

Class

Build class containing the build. A default build class name is displayed if one is not assigned

User

User who started the build and the machine where the build was invoked. (Mouse over the field to see the IP address)

Start Time

Date and time when the build was started

Duration

Build duration (the elapsed time between the start and end time)

Status

Build’s result or status:

Paused by a breakpoint

Running

Completed successfully

Agent availability (using a percentage bar) during a running build. On mouse over, Requested indicates the number of separate build steps for which eMake identified and requested agents

Timed out. For details about possible causes, see KB article KBEA-00039 “ Fixing builds that the Cluster Manager reports as timed out.”

Stopped manually

Failed or encountered an error

Running but waiting for a build license. This appears when the number of concurrent builds has reached the license limit. The build will resume when another build stops running for any reason (because it completed successfully, completed with an error, was stopped from the Cluster Manager, timed out, and so on).

Platform

Operating system platform of the machine running the build:

Linux

Windows

Priority

Build priority for acquiring agents when the build runs:

image::priority-high.jpg[23,22] High (three green bars)

image::priority-normal.jpg[22,19] Normal (two yellow and one white bar)

image::priority-low.jpg[21,21] Low (one blue and two white bars)

Actions

Opens the Messages page for viewing all system log entries for the build

Deletes a non-running build

Stops a running build