Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Pipelines are not triggering after I pushed the configuration file to my feature branch Edited

I created the configuration file for pipelines and put it to the root of my project as `bitbucket-pipelines.yml`. It looks pretty much like the gradle template from the pipelines setup page.


I expected the build to trigger immediately after I push the configuration in my feature branch but nothing happened. Do I first need to have the configuration pushed to master? If so, how do I test that the pipeline is working correctly? Because I would like to avoid committing broken code to master.


All I am seeing in the pipelines page is the welcome text with examples, although I have the configuration file in the root of my project. Please, note that the configuration file is only in my feature branch at the moment.


5 answers

Seems like an old thread but pipelines where being triggered yesterday, but today they are not - therefore I can only assume that something has been changed by the BitBucket team. 

Is now always required to manually select to run the pipeline and select the branch, although our pipelines are designed to run on specific branches?

Or can we re-enable the trigger to run the relevant pipeline when merging code in develop/staging/master?

We are experiencing a very similar issue here, our pipeline used to trigger until yesterday when pushing on master, now we have to start it manually.

same here, if anyone figures out how to fix it that would be appreciated

1 vote

Hi Martin,

Can you attach a copy of your YAML here so we can double check the configuration?




Sure, I please find the file below:


image: openjdk:8

- step:
- gradle
- bash ./gradlew clean build





Can you check if your webhooks are firing, and if they're returning any error messages.

They're located in your repository settings -> workflow -> webhooks

Screen Shot 2018-07-31 at 4.43.16 pm.pngScreen Shot 2018-07-31 at 4.43.22 pm.pngScreen Shot 2018-07-31 at 4.43.59 pm.png


I am seeing some Pipelines entries in my Webhooks:


When I click on the logs, they are empty, though...

EDIT: it just loaded. It shows history of repository edit, pull request updates etc. But I added my script just yesterday and these records dates back weeks ago so I assume that these are different pipelines.

Can you verify Pipelines is enabled?

Screen Shot 2018-07-31 at 4.58.08 pm.pngScreen Shot 2018-07-31 at 4.58.11 pm.pngThere's a bug we identified that related to onboarding. We'll start working on a fix, but lets try to get a workaround for you first. :)

Yes, I checked that yesterday. Pipelines are enabled in the settings :)

Goodo. :)

At this stage I think you have two options:

  1. Commit a bitbucket-pipelines.yml file to master (it can be a trivially simple one) to work around the bug we found. That should hopefully let you see your actual pipelines, rather than the onboarding screen.
  2. Wait a few days for us to get a fix out (it's after office hours now, so work on a fix won't start until tomorrow). I've brought the bug into our sprint, though. So we'll look at it ASAP.

Sorry you got hit by this.

Alright, I will try to propagate it to master, but it probably won't be today, since we keep our master branch locked and only work with it during release so your fix might be coming sooner :)


I will test it on different repository in the meantine and keep this issue open until the fix is ready. Thanks for your cooperation!



Is there any updates on this issue? I faced the same behaviour.

However I can see pipelines in "Schedule" popup and can setup periodical builds. Just curious what would happen if I do that. But I still need to have builds on push.

Oh, it worked eventually. Builds appeared after ~30 mins.

Hi @strngr

You encountered an issue unrelated to this question. We were having performance problems when you saw the delays.

If it reoccurs, I suggest you look at our StatusPage, as it's likely unrelated to this question (it was opened in July). By the time we have a chance to respond to Community questions, the issue would hopefully be fixed. :) StatusPage will give you more up to date comms on what's going on.



Hi @Philip Hodder

I am also facing the problem that the pipelines are not triggered automatically after I push something to the master branch (which has a pipeline configured which used to be triggered automatically ) Any ideas/ suggestions? 

Is this problem still occurring for you? If so, can you add in your YAML configuration here?

Did you previously had working pipelines, or are you just setting up a new repository?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

770 views 15 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you