* Global build view: The default view, displays builds for all pipelines for all projects across your organization.

* Project build view: Selecting a project displays the builds for the pipelines in the project.

As a user, you can see builds from all pipelines you have access to. If your permissions do not include access to specific pipelines, you will not see builds from those pipelines.

As a user, you can see builds from all pipelines you have access to. If your permissions do not include access to specific pipelines, you will not see builds from those pipelines.

Each screen contains all builds sorted from the most recent to the oldest. The first time you visit

the screen there are no filters defined. To narrow the list, use the filters on the top

of the screen.

The Builds page for a pipeline displays by default all builds sorted from the most recent to the oldest. To narrow the list, you can use the date range filter, and additional filters at the top of the page.

{% include

image.html

max-width="80%"

%}

Each build's status is displayed beneath the build details, identifiable by a distinct icon. Refer to the table below for a description of the various statuses associated with pipeline builds.

Directly above the list you can find several filters.

{: .table .table-bordered .table-hover}

| Pipeline Build Status Icon   | Description|

| ------------------------| ----------------|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-running.png"display=inline-block/> {:/}| Pipeline build is currently running.|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-successful.png"display=inline-block/> {:/}| Pipeline build completed successfully.|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-delayed.png"display=inline-block/> {:/}| Pipeline build run has been delayed as there are no free builders. <br>A build can be delayed for a maximum of seven days. Each account can have up to a 1000 delayed builds at any time. <br>{::nomarkdown}<b>NOTE</b>: <ul><li>Builds that are delayed for more than seven days are terminated with a_Delay time limit exceeded_ reason. </li><li>If the total number of delayed builds for an account exceed 1000, older builds are terminated with a <i>Maximum delayed workflows exceeded</i> reason.</li></ul>{:/}|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-pending-approval.png"display=inline-block/> {:/}| Pipeline build is pending approval.|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-denied.png"display=inline-block/> {:/}| Pipeline build pending approval has been denied approval.|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-terminating.png"display=inline-block/> {:/}| Pipeline build is gracefully terminating execution.|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-terminated.png"display=inline-block/> {:/}| Pipeline build execution has been manually or automatically terminated.|

|{::nomarkdown}<imgsrc="../../../images/icons/pipeline-build-failed-error.png"display=inline-block/> {:/}| Pipeline build execution has failed because of errors.|

At the most basic level youcan choose between

The**Add Filters** option allows youto filter the list of builds by additional criteria, including build status.

**Running* builds that are currently executing

**Pending* builds which are queued and waiting to start

**Delayed* builds which cannot run yet, because there are no free pipeline builders.

A build can be delayed for a maximum of seven days, and each account can have up to 1000 delayed builds at any time.

* Builds that are delayed for more than seven days are terminated with a_Delay time limit exceeded_ reason.

* If the total number of delayed builds exceed 1000, older builds are terminated with a_Maximum delayed workflows exceeded_ reason.

At the most basic level, you can filter by status, choosing between Running/Pending/Delayed builds.

**All* builds regardless of running stage (this is the default)

You can further filter the builds by choosing the various filter types that specify the build job.

Notice that all filters are multiple-choice so you can select multiple values for each filter category.

At any given point you can see all the active filtersontop of the screen.

At any given point you can see all the active filtersat thetop of the page the screen.

{% include

image.html

From the step details you can also click on the yaml tab to see the yaml segment for that individual step: