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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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 limitations Edited

Hello everyone,

We have recently activated Bitbucket and one of the dev. came up with these limitations. Anyone care on commenting these?

I spent some time with Pipeline and I think it is too limited and we will need to continue with CircleCI. Here the list of limitation:

  • Doesn't support starting a pipeline when a PR is made using a fork repository (this is our current way of working), this could be mitigated by using GITFlow instead of fork.

  • Pipeline deployment is limited to 10 environments and doesn't scale when we are using mono-repo since we have multiple deployments per repository, e.g. at the moment XYZ would require 15 environments. Composer/Front-end would have the same issue and probably worse.

  • Pipeline deployment variable cannot be shared across steps, so if you want to read a private key in more then 1 script you are doomed (or have to use some archiving hack)

  • Pipeline YAML anchor (shared scripts) don't support passing variables (e.g. calling the same YAML script with different parameters)

Thanks for your feedback!

Gabriel

1 comment

Hi, we also have this problem as  we currently have more that 20 websites and the plan is to have about 100 websites so we really need to increase the limit

Can someone of support comment this and help us?

This limit wasn't enforced until recently it seems:

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.

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

503 views 6 4
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