Unable to configure pipelines after deleting the bitbucket-pipelines.yml file

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

Summary

After deleting the bitbucket-pipelines.yml file, users are unable to configure Pipelines.

Environment

Bitbucket Cloud Pipelines

Diagnosis

Sometimes, users can, intentionally or not, delete the bitbucket-pipelines.yml from the main branch of the repository.

With that, if the user navigates to the Repository Settings > Pipelines > Settings and clicks on the Configure bitbucket-pipelines.yml button, the user will see a spinning page like the one below:

(Auto-migrated image: description temporarily unavailable)

Cause

This happens because the repository tries to find the bitbucket-pipelines.yml to configure, but there is no file available.

Solution

It's possible to solve it by pushing the file back to the repository. You can achieve that with the commands below:

1 2 3 4 $ touch bitbucket-pipelines.yml $ git add bitbucket-pipelines.yml $ git commit -m 'Add bitbucket-pipelines.yml back to remote' $ git push

Updated on March 21, 2025

Still need help?

The Atlassian Community is here for you.