Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to edit bitbcuket-pipelines.yml in Bitbucket

I have created a bitbcuket-pipelines.yml and committed and push this in my root directory. When making changes in my repository, my build is triggered so no issues there. The problem is that when I click the 'Configure bitbucket-pipelines.yml' button on the 'Pipeline settings' screen, I just get taken to a page that says "Hooray! You've successfully set up pipelines"...



I can see in the developer tools that the call to fetch the YAML file from my master branch returned a 404 so I think there is something wrong behind the scenes with Bitbucket. I 100% have a bitbucket-pipelines.yml file in the root of my repository by the way.

2 answers

I'm getting exactly the same issue right now.

0 votes

Hi @Andy_Furniss

I was trying to reproduce this scenario and I was able to do it with by either removing the pipelines file or renaming it with different caps like Bitbucket-pipelines.yml (capital "B"). It could be any change that makes the file different from bitbucket-pipelines.yml which is the right name for it.

Can you confirm the file name is exactly bitbucket-pipelines.yml ?

The problem you are facing might not be exactly the same since I get a 403, not a 404.

I'm just wondering if it could be the same issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events