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

Scheduled Pipelines runs multiple times on same commit

Hi everyone,

I've set up Bitbucket Pipelines for my repositories, I'm using scheduled pipelines to run unit tests and regression tests overnight.


The current problem is that the scheduled pipeline runs multiple times for the same commit. This is wasting my minutes and would like to know if there is any known way to stop this from happening.


Here's my bitbucket-pipelines.yml:

image: ruby:2.4.0

      - step:
- do stuff

Thank You.

3 answers

Gabriel, I know this is an old thread, but did you solve your issue? I am having a similar problem. Thanks!

0 votes

Adding onto Aneita's response. You can use the Bitbucket REST API as a workaround if this is important functionality for you. But this will be a bit more work to set up (and may not suit your specific use-case).

You can use the build status API to check if another Pipelines has been run against the commit that's currently being tested. At the start of your pipeline you can check this and then stop earlier if there's already a pipeline against that commit.

Build Status API:

0 votes

Hi Gabriel,


There currently isn't a way to prevent scheduled pipelines from running on the same commit. We do have an open request to improve this. I encourage you to vote for that issue and add a comment with your use case if it is something that you would like to see. 




Suggest an answer

Log in or Sign up to answer

Atlassian Community Events