# Overview


This page gives an overview of all the pipelines that belong to your organization.

By clicking on the pipeline name, you will be automatically redirected to the pipeline details view, showing also the resources.

Using this overview, you are able to quickly know the status of your pipeline with the color code, but also checking how long this status hasn't changed.

# How the status is defined ?

To know the status of a pipeline, we are checking if a job has a different status than "success".

The order to determine this status is:

Build Running > Paused > Failed > Errored > Aborted > Succeeded

Pending status is displayed only if there is no other build status and every other builds are still in pending status.

# How is the order determined in the pipeline grid

Pipeline Grid

The pipeline grid is computing the rank and dependencies on your pipelines jobs.

For example, on the image above, it represents a Terraform Runner pipeline. There are 3 jobs:

  1. terraform-plan
  2. terraform-apply
  3. terraform-destroy

The terraform-destroy job is defined in a specific group, but if we take a global overview of the pipeline, it has the same dependency than the terraform-plan: it needs the Git repository containing the Terraform code.

The job terraform-apply depends on the job terraform-plan. As it has a dependency on a rank 1, it will be placed on a rank 2.

Therefore, we have 2 different ranks:

  1. terraform-plan + terraform-destroy
  2. terraform-apply

As you can see, with those ranks, we can create a grid that will mimic the look of your pipelines, from the left to the right.

To know quickly which job is failing, you can put your mouse over, it will show a tooltip with the job name.

Clicking on it will redirect you automatically to the last build of this job.