Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I remove this ugly pipeline thing I just created

Alan Holden
July 14, 2026

So I thought I had followed the Getting Started instructions to create my first pipeline.

But now the UI for this creation is filled with red error icons, and messgaes read as though I had intended my first one to affect our master repo. Definitely not my intention.

So, how do I simply remove this malignancy and go back to the days where I never "Got Started"? I just want to begin again, trial and error, without consequences like this.

TIA, AL

HOW DO I DELETE THIS CRUD?

2026-07-14_15h29_20.png

 

1 answer

0 votes
Ajay _view26_
Community Champion
July 14, 2026

Hi @Alan Holden 

The red errors are just the pipeline config being invalid (probably missing required fields or bad YAML indentation). No damage done to your actual codebase. Pipelines don't modify your source code; they only run CI/CD steps on it.

Here's how to remove it:

  1. Go to your repository in Bitbucket Cloud.
  2. Find the bitbucket-pipelines.yml file in the root of your repo (it'll be in the source view).
  3. Delete that file and commit the change. That alone stops any pipeline from running.
  4. Then head to Repository settings > Pipelines > Settings and toggle the "Enable Pipelines" switch off.
  5. That's it — you're back to square one
Alan Holden
July 14, 2026

Thanks @Ajay _view26_ for the response! 
There was no  bitbucket-pipelines.yml file in any branch, so I created one and placed this minimal config inside.

image: atlassian/default-image:3
pipelines:  
default:

- step:
name: Build
script:
- echo "Pipeline configured"


I'm not sure if I'm technically back to square one, because the items listed in the "Pipelines" page are still there... and pipelines was enabled back then.

Before I "Got Started", there was nothing here... or there.

But at least the red complaints have stopped... and I'll always have this lifelong reminder of something I probably should've paid someone else to do - rather than believing it was easy - and that a little "tinkering" would be easy to undo ;-]

Does anyone know why BitBucket would assume I wanted to kick off my first newbie attempt under our master production branch, rather than asking me first? Are all Pipelines supposed to go there alone?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events