You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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?
At this stage I think you have two options:
Sorry you got hit by this.
Same here, no automatic triggers for some repos since 27th May. Other repos work fine. Checked bitbucket-pipelines.yml (valid) and pipelines are enabled in settings. In the webhooks of repos in question the history of requests to pipelines endpoint is empty. Would appreciate a fix, because we rely on the pipelines heavily :(
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.
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!