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

Bitbucket deployments limit Edited



It says I cannot have more than 10 deployment enviroments for my repository

How come? what´s the reason for the limit?


thank you!

2 answers

1 accepted

1 vote
Answer accepted

Hi Jens,

Currently, we restrict the number of deployment environments to 10, as it's also the maximum number of steps that can run in a single pipeline.

We have an open feature request to bump the maximum number of steps in a pipeline.

If you'd like, you can also open a feature request to specifically bump the maximum number of environments in a repository.

Did you have a particular use-case in mind for having more than 10 deployments environments?





We are not having a normal use-case I guess.

We run a mono repo with several microservices, so there aren´t really more than 3 steps per branch usually, but a lot of dedicated microservice branches


Of course I would like to have more than 10 enivornments. But I don´t know what the hassle would be from your side?


I have no interest in running 10 in a single pipeline, just more than 10 overall. So I don´t even know if this implementation is different from open feature request you referenced


Thank you


Like Taras Zoshchuk likes this

Thanks for the information. Yeah, this would be a different feature request. Independent of the step limits. I'll pass this information on to our product managers. If you'd like, you can open a feature request for this with the details you just shared.

Seems this new deployments limit has an unintended side effect of blocking3rd party deployment services, like Laravel Forge the limit enforces 50 now, we had 45 before this change when it said the limit was 10...

@Philip Hodder

I can see the limit has been increased from 10 to 50. We already use 48 deployment environments (which isn't in BitBucket yet) at the moment and we are going to soon outnumber the value of 50. So if we are planning to use BitBucket pipeline, we will need to choose a future proof solution where we can add more deployment environments which isn't possible at the moment.

Is there a potential that the limit could be increased? If we know that it is going to be available in the future, then we shall start using BitBucket pipelines for now.

Also I am interested to know is there a reason for the limit of 50 deployment environments? Please let us know.

Suggest an answer

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

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

266 views 2 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