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
Seems this new deployments limit has an unintended side effect of blocking3rd party deployment services, like Laravel Forge https://bitbucket.org/blog/additional-deployment-environments-for-bitbucket-pipelines the limit enforces 50 now, we had 45 before this change when it said the limit was 10...
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
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