Pipelines

Use the Pipelines tab to monitor and manage Bitbucket pipelines.

Navigate the Pipelines tab

When more entries are available, use Load more at the end of the list.

In the activity panel, Run Pipeline, the Show filters icon, and More actions share the title row with the source badge.

To open the Pipelines tab, click DevOps > Pipelines.

Pipeline runs are listed chronologically and display the following information.

• Status icon: Indicates if a pipeline run is in progress, paused, completed, queued, or skipped.
• Title and pipeline number: The custom pipeline that ran, or Pipeline for a branch or tag pipeline, and the build number.
• Ref: The branch or tag that the pipeline ran on.
• Trigger: What started the pipeline run, for example a push or a manual run.
• Commit: The commit that the pipeline ran on. The activity panel does not show it.
• Timestamp: When the pipeline run finished, or started if it is still running.

Click a pipeline to open the pipeline detail tab. A card at the top of the tab shows the pipeline status and these facts: Ref, Commit, Custom pipeline (when a custom pipeline ran), Started, and Duration. Click More details to show Trigger, Creator, and Updated. Click Fewer details to hide them. Bitbucket does not report the variables that a run started with, so the detail tab cannot show them.

The detail tab lists the steps of the pipeline as cards with their status and duration. Steps that run in parallel are under the Parallel group heading. To open a step, click the chevron at the left of the step or click its name. Click it again to close the step. An open step shows its Status, Started, Duration, and log. You can open more than one step at a time, for example to compare two logs.

Click Stop to stop a running pipeline. Bitbucket cannot stop a pipeline that is paused at a manual step, so Stop is unavailable for it. Click Run again on this commit to start a new pipeline on the same commit. It runs the branch or tag pipeline, not a custom pipeline, and sends no variables. The new pipeline gets a new build number.

To open a pipeline in a separate tab, right-click the pipeline and click Open in New Tab.

Pipelines from another repository

A pull request’s pipeline badge can open a pipeline that ran in another repository, such as a fork. The detail tab shows that pipeline from its repository and adds a Repository fact with the repository’s name. If Bitbucket reports that you do not have write access to that repository, Stop and Run again on this commit are dimmed. Point to one to see the reason. If Bitbucket does not report your access, the actions stay available, and Bitbucket refuses an action that you cannot take. If your account cannot read that repository, the tab says so and offers Open on Bitbucket.

To open the page on Bitbucket, click the source badge at the right of the tab header, then click Open on Bitbucket.

Filter pipelines

Click the Show filters icon to open the filter panel. Bitbucket applies each filter to all of the repository’s runs, not only the loaded ones.

• Status: In Progress, Pending, Paused, Successful, Failed, or Stopped. A run that waits at a manual step is Paused.
• Branch or tag: Type the full name. The name must match exactly, including case.
• Trigger: Push, Manual, or Scheduled.
• Pipeline: A custom pipeline. The list shows the custom pipelines of the main branch and of the loaded runs. It does not show when there are none.
• Creator: The person who started the run. It shows when the loaded runs were started by two or more people.

Press Ctrl+F (Cmd+F on macOS) to open the panel and focus Branch or tag. When the panel is too narrow for the icon, click More actions > Show Filters.

The line above the list says how many pipelines there are: N pipelines with no filter, or N matches with one. Each filter that is set shows as a chip above the count, for example Status: Failed. Click a chip to open the panel at that filter: a list opens, and a text field gets the cursor. Click its x to remove the filter. To remove all of them, click Clear filters at the end of the count line. In a narrow panel the button says Clear. The filters stay while Zide is open. When you start Zide again, no filter is set.

Run a pipeline

1. In the Pipelines tab, click Run Pipeline.
2. In the Run Pipeline dialog, the Branch or tag field shows the current branch. To run on a different branch or tag, enter or select it.
3. In Pipeline, select the pipeline to run:
   • Branch pipeline is the pipeline that a push to the branch starts: the branch’s entry under branches, or default. For a tag, this is Tag pipeline: the tag’s entry under tags.
   • Under Custom, select a custom pipeline from the bitbucket-pipelines.yml of the branch or tag.
4. If the custom pipeline has variables, set them under Variables. A field shows the variable’s default, and its description below it. A variable with allowed values is a list. A variable without a default needs a value, and a red asterisk (*) marks it.
5. Click Run.

The field lists the repository’s branches and tags. Type to search, or click the list button or press Down to show the list. If a branch and a tag have the same name, choose one from the list. If the field is empty or the repository does not have the name, a message shows below the field and Run is unavailable. Point to Run to see the reason. Run is also unavailable when Zide cannot check whether the name is a branch or a tag, and until each variable that needs a value has one. If you leave a variable with a problem, a message shows below it.

Zide reads bitbucket-pipelines.yml from the branch or tag when the dialog opens and when you change it. If the new branch or tag also has the custom pipeline that you selected, it stays selected. Otherwise, the dialog selects Branch pipeline or Tag pipeline and says why. If the file is not valid YAML, the dialog says so. Branch pipeline stays available, but Bitbucket fails the run until the file is fixed. If Bitbucket does not start a run, the dialog shows the reason. Pipelines must be on for the repository: in Bitbucket, open Repository settings > Pipelines > Settings.

Zide does not write variable values to the App Console. Bitbucket shows them on the run’s page on Bitbucket.

Zide Assist can also list the custom pipelines on a branch with their variables, and run a branch pipeline or a custom pipeline with variables.

Assist with This

Right-click a pipeline, or its detail tab, and point to Assist with This.

Under Zide Assist, click Add to Conversation to attach the pipeline to a Zide Assist tab. You can also drag the pipeline into a Zide Assist tab. For more information, see Attach items to a message.

Under Ask Zide, click Open Ask Zide. Zide opens the pipeline in its detail tab with an Ask Zide panel beside it. In the panel, click Summarize Outcome or Explain Failure. Explain Failure is unavailable when the pipeline has no failed job. When a job failed, Explain Failure is first. Ask Zide does not run or stop the pipeline. See Ask Zide beside a tab.

Activity indicator

The activity icon is blue while a run is running or queued, amber when waiting for user action, and red for a failure on the current branch. Successful runs leave the icon neutral.

The indicator follows the newest commit with pipeline runs on the current branch. A newer commit starts with its own results. By default, a failure stays red while that commit retries, until it succeeds. To clear failure indicators when viewed, turn off More actions > Failure indicator > Keep failure indicator after viewing. This preference is shared by Actions and Pipelines across projects and persists across restarts.

Run and step status icons use blue for running or queued work, amber for paused work, red for failures, and green for success. Stopped, halted, and unknown results are neutral.