Scaling in Bitbucket Cloud: new features and reliability numbers

Post by vorg » Thu, Oct 13, 2016, 8:12 PM UTC

agentgt wrote: post #29

We use Bitbucket (for over 4 years now) and in general like it mainly for its pricing model. However I have the (generally unfounded) fear that it will become bloated and slow like several other Atlassian products. I have really grown to dislike Jira but I will save that complaint for some other time. The Bitbucket UI has improved over time but my real annoyance is the " Recent Activity " list is not wide enough and…

> heavily invested in Jenkins + Bash and will probably use Jenkins pipeline (Groovy) in the future ... would prefer a scripting language over YAML

Do you really want to switch to Apache Groovy? Bash is pretty standard for scripting *nix whereas noone knows what the standard is for scripting the JVM?

Post by brazzledazzle » Fri, Oct 14, 2016, 3:42 PM UTC

iamaelephant wrote: post #33

brazzledazzle wrote: post #16

Earlier quoted context omitted.

Might want to check and see how far behind you are in upgrades. Even though the on-prem version will never have feature parity (new features hit cloud first) it could be that whoever runs your instance hasn't upgraded in a little while.

Feature parity is not really a goal of these products - they are totally separate teams, technologies and languages. If one team develops something awesome then of course the other will try to reimplement, but it's not really the case that features "hit cloud first".

You're saying the BitBucket cloud and server teams are using totally separate technologies and languages? That's not the impression I've gotten at all at every atlassian conference I've been to. Seems wasteful but nothing surprises me anymore.

Re: Scaling in Bitbucket Cloud: new features and reliability numbers

Re: Scaling in Bitbucket Cloud: new features and reliability numbers