Scaling in Bitbucket Cloud: new features and reliability numbers
blog.bitbucket.org
Scaling in Bitbucket Cloud: new features and reliability numbers
1–10 of 42 posts
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#2I've used and loved bitbucket for years for private project hosting, but for the occasion where I need to put more devs on a particular project I'm not sure why I would pay for it now over using gitlab for free. It might be different if it was 5 users per project for free, but 5 collaborators across all of my projects is just too limiting - especially when I can get everything bb has and more from gitlab.
At the same time I understand bb needs to make money - hopefully they'll make enough to keep up the competition.
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#3Doesn't really matter that they've made Pipelines available for all users when it's lacking some pretty basic functionality. Like the ability to do something on failed builds.
But other than that it looks really good and responsive. Going to be interesting to see how the influx of new users will impact the average build time.
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#4I've used and loved bitbucket for years for private project hosting, but for the occasion where I need to put more devs on a particular project I'm not sure why I would pay for it now over using gitlab for free. It might be different if it was 5 users per project for free, but 5 collaborators across all of my projects is just too limiting - especially when I can get everything bb has and more from gitlab. At the same…
> I understand bb needs to make money
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#5Doesn't really matter that they've made Pipelines available for all users when it's lacking some pretty basic functionality. Like the ability to do something on failed builds. But other than that it looks really good and responsive. Going to be interesting to see how the influx of new users will impact the average build time.
Hi vegardx, I'm the lead Product Manager on Pipelines. First of all, thanks for your comment. It's still early days for us but we've had some great feedback from beta customers and making it available to all customers allows us to help a lot more teams on Bitbucket. Regarding the failed builds you can use webhooks [1] today to trigger actions after the pipeline completes and we'll work on extending this capability in the future.
Our first focus was to make a platform that can scale on demand without hard constraints on the number of containers running. We know that we have some gaps to fill but we're now moving fast and we've added several features in the past weeks (repo status, notifications, pipelines statuses everywhere).
Thanks again for your feedback. Let me know if you have any questions.
Sten
[1] https://confluence.atlassian.com/display/BITBUCKET/Notificat...
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#6I was recently looking at BitBucket Data Centre, to move our in-house git server to something with better clustering & high-availablilty & failover (rather than doing it ourselves). I was a little disappointed to find out the HA features are provided by storing your repos on an NFS server, and detaching/attaching it to the primary node.
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#7I was recently looking at BitBucket Data Centre, to move our in-house git server to something with better clustering & high-availablilty & failover (rather than doing it ourselves). I was a little disappointed to find out the HA features are provided by storing your repos on an NFS server, and detaching/attaching it to the primary node.
Bitbucket PM here, sorry to hear this doesn't suit you. Could you tell me more? If like to better understand your concern.
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#8I've used and loved bitbucket for years for private project hosting, but for the occasion where I need to put more devs on a particular project I'm not sure why I would pay for it now over using gitlab for free. It might be different if it was 5 users per project for free, but 5 collaborators across all of my projects is just too limiting - especially when I can get everything bb has and more from gitlab. At the same…
Have you noticed any drawbacks to using Gitlab over Bitbucket/Github?
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#9The Bitbucket UI is a mess.
* It takes over your native browsers find feature.
* It's javascript heavy and has multiple panes that scroll, collapse, and expand.
* Viewing diffs requires you to click each file that changed (unlike every other diff/code browser I've used where it has one long page with all the changes)
Re: Scaling in Bitbucket Cloud: new features and reliability numbers
#10The Bitbucket UI is a mess. * It takes over your native browsers find feature. * It's javascript heavy and has multiple panes that scroll, collapse, and expand. * Viewing diffs requires you to click each file that changed (unlike every other diff/code browser I've used where it has one long page with all the changes)
> * Viewing diffs requires you to click each file that changed (unlike every other diff/code browser I've used where it has one long page with all the changes)
This is not my experience. Picking a random project I see a listing of all changes in all files: https://bitbucket.org/atlassianlabs/asap-cli/pull-requests/3...
That's for a pull request, this is for a branch: https://bitbucket.org/atlassianlabs/asap-cli/branch/bump_dev...