Repository shows 0 builds on Source tab

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

  • This knowledge article provides the most common reason behind this issue occurring, and an explanation as to why this may occur

Diagnosis

  • The repository build status in question shows 0 builds, however many pipelines were run and the pipeline page of the repository shows the builds that were run:

    (Auto-migrated image: description temporarily unavailable)

Cause

  • The repository build status in the source page is determined by the last commit made on the branch configured as the main branch for the repository. Bitbucket checks the last commit on the main branch and verifies the build status.

  • Additionally, Bitbucket only displays the last Build status Icon on the Repositories page and Repository list if the bitbucket-pipelines.yaml file exists in the branch configured as the main branch and:

  1. Has a trigger to the "main branch“ in the branch section

    OR

  2. Has a “default” trigger

  • If the last commit on the master/main branch has a [skip ci] commit message or the build does not run on the last commit for any reason, there will be no build information on the repository list. This is because the latest commit doesn't have any build associated, hence the Repository Source view as well as the Repository List view won't show the build status.

If you require further clarification on the topic described within this article, please raise a support ticket or raise a community support ticket for assistance with this.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.