Continuous Integration Visibility Explorer

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.


The CI Visibility Explorer allows you to search and filter, visualize, and export pipeline executions at multiple levels using any tag.

Navigate to Software Delivery > CI Visibility > Executions to see your CI pipeline execution results across the following levels: Pipeline, Stage, Job, Step, and Command.

Default CI facets

The CI panel on the left lists default facets you can use to search for your pipeline executions.

CI StatusThe status of the CI execution: Success , Failure, or Canceled.
CI InstanceThe instance name of the CI provider.
DurationLength of time for the pipeline to execute.
Pipeline IDThe ID of the pipeline.
CI ProviderThe name of the CI provider.
Node LabelsThe labels of the node.
Node NameThe name of the node.
Partial PipelineRefers to CI pipeline executions that include retries, manual approvals, or other incomplete sequences.
Partial RetryIndicates whether the CI execution was a retry of a previous execution.
Manually TriggeredIndicates whether the CI execution was manually triggered.
ParametersThe user-defined parameters when a pipeline or job triggers.
Pipeline NumberThe number of the pipeline.
Pipeline URLThe URL of the pipeline.
Queue TimeThe total duration a job or task spent waiting in the CI queue before execution.
DeploymentThe GitLab environment deployed with a CI pipeline.
Deployment ActionThe action taken within GitLab’s deployed environment.
Command NameThe user-defined identifier for a specific command within the CI pipeline.
CommandThe command line that was run to generate the custom pipeline span.
Downstream PipelineIndicates if this pipeline is downstream of another pipeline.
Upstream Pipeline IDIdentifier for the pipeline execution that precedes and triggers the current pipeline.
Step NameThe name assigned to a specific step within a CI pipeline.
Error DomainThe type of error for a CI execution such as a provider, user, or unknown.
Run timeThe total duration spent executing the CI pipeline.
Wait timeThe total time spent waiting for manual approval within a CI execution.
Is DeploymentIndicates whether a job within the pipeline initiated a deployment.
Contains DeploymentIndicates whether the pipeline includes any jobs that trigger a deployment.

For more information about common facets that you can use as part of your search query in the CI Visibility Explorer, see Pipeline Execution Facets.

Pipeline executions details and traces

You can see aggregated data about pipeline executions over the selected time frame. Use the search field and facets to scope the list down to the executions you want to investigate. Change the list to show pipelines, stages, or jobs using the buttons at the top.

Below are three graphs that visualize the durations of your most active pipelines, your failed pipelines over time, and the executions of your pipelines with an option to toggle to accumulated duration, respectively. These graphs are scoped to the level chosen at the top left (Pipeline, Stage, Job, and more.)

Explorer view trend graphs for Duration, Errored, and Executions

Each pipeline execution is reported as a trace, which includes stage and job information. Access individual pipeline, stage, and job execution traces by clicking on an execution in the list (similar to clicking into a pipeline execution from the Pipeline Details view).

CI pipeline data is available in dashboards and notebooks, enabling build engineering teams to customize their communication about high-priority work and CI trends over time.

Search and filter

You can narrow down, broaden, or shift your focus on a subset of pipeline executions by clicking on the facets to the left or writing your own custom query in the search bar. When you select and deselect facets, the search bar automatically reflects your changes. Similarly, you can modify the search bar query or write a query from scratch in the search bar to select and deselect the facets on the left.


Group your queried pipeline executions into higher-level entities such as fields, patterns, and transactions in order to derive or consolidate information. By using facets, which you do not need to create to search for attributes, you can accomplish the following actions:

  • Search and keep track of the progress of tests running in a CI/CD pipeline.
  • Investigate every CI/CD job execution to identify and troubleshoot failing test runs.


Select a visualization type to visualize the outcomes of your filters and aggregations and better understand your pipeline executions. For example, you can view your pipeline executions in a list to organize your pipeline data into columns, or in a timeseries graph to measure your pipeline data over time.


Export your view in the CI Visibility Explorer to reuse it later or in different contexts.

Further reading