PM for Bitbucket pipelines here, my team of ~20 owns that feature E2W, would genuinely love to chat, share some stuff we're working on, and get feedback/thoughts.
Ping me if you're open to chatting emunday@atlassian.com
I'm glad you're working on BB. We switched to GitHub a year ago and are happy with it, but with a slightly better UI and more reliable/advanced CI/CD features, I might not have been able to justify the switch.
Bitbucket used to fall over for monorepos. Sometimes it would fall into a death spiral, sometimes it would attribute PRs and commits to the wrong engineers (!!!) Not sure if that's still the case, but it was awful working with it.
Don't even get me started on the dumpster fire that is Jira.
We 100% have had issues with larger repo's in the past while we were still hosted on a stand-alone data centre. Since finishing our migration to AWS ~12 months ago, all stability and performance metrics are substantially improved.
Full disclosure, we do still have some work to do in terms of supporting very large repo's (>10GB non-LFS) - but those scenarios are still handled relatively gracefully.
Just an FYI - we (Bitbucket cloud) recently shipped changes to the PR experience (rebuilt the PR diffing algorithm) which has increased the speed by ~95%.
100% aware we still have a way to go on performance, but we're literally orders of magnitude faster than even 12 months ago, with another order of magnitude on the cards this year, especially for larger customers (250+ users).
Can you please share why you don’t have a file list on a left panel (like in IntelliJ, Windows Explorer or even Bitbucket DC) while reviewing PRs? Do stats show that people prefer to be shown a long diff with a tiny tab on the top-right that shows the list of files?
Wouldn’t that be a UX worth improving? (For us, we’ve attempted the move 3 times, but developers keep rejecting BBCloud because of the annoying UI - mostly the missing treeview to navigate files).
To be 100% honest - I don't have an answer for you on that. My teams focus primarily on CI/CD and the new extensibility tooling we're building (allowing customers to basically add their own features specific to their use-cases, like the plugin system for Server, but simpler).
If you shoot me an email I can connect you with the PM who manages the PR experience directly - they're doing a lot of design work in this space and would be really keen to talk.
You still don't have basic features like Syntax Highlighting in Diffs.
Yes yes, you are promising it soon in an Experimental Labs release, but it's been 11 years. It's laughable and who knows if that will tank performance again.
You had a solid PR tool on bitbucket server and somehow took that and made it 100x worse on Bitbucket Cloud. The File picker and the way you navigated between files with keyboard shortcuts were GREAT.
Bitbucket Cloud is just a copy of a really old version of the Github PR viewer, but with a lot more problems and no updates.
GitLab has probably 5x as many features as Bitbucket. For example you still need a ticketing system with Bitbucket (Jira), but not with Gitlab since its issues system is self contained.
I use Bitbucket at $job. They do have CI/CD now, it's called Bitbucket Pipelines. It's not bad, not great. For better or worse, I always measure version control hosting against GitHub which is still the king in my opinion. There are so many little things that GH has which BB doesn't. When you add them all together, it's easy to see why you'd want to switch to GH or something similar.
Examples:
GH lets you write comments/feedback on a PR and then submit it (sort of like staging the comments) in one fell swoop. With BB, each comment triggers a notification to the PR author.
GH has draft PRs. Debatable how useful these are, but people definitely like them on GH and that's not an option on BB.
GH has built-in support for Mermaid in markdown, BB doesn't and won't ever.
GH Actions generally seem more flexible. BB, for example, doesn't let you call a custom "Pipe" when using your own Mac OS runner in BB Pipelines — something you need to do if you want to build Apple projects — which is just a strange and frustrating limitation.
There are so many other things. In general, BB is just slow and janky as almost all Atlassian products are. Every time you click to complete or submit something, you just experience slowness.
I'd switch to GH in a minute if we could, but our team already uses so much other Atlassian crap that we're kind of stuck with it at the moment.
I'm using BitBucket at work and it seems like it's no longer "one comment - one notification". When adding the comment to the PR there's "Start review" button, so and at the end you just click "Finish review" and everything goes as one notification.
PM for Bitbucket pipelines here, my team of ~20 owns that feature E2W, would genuinely love to chat, share some stuff we're working on, and get feedback/thoughts.
Ping me if you're open to chatting emunday@atlassian.com
I use it (old self hosted and cloud. Also GitLab and GitHub on a regular basis.)
BitBucket is ok.
It doesn’t have nearly the same feature set as the others. You have to bring on more of the Atlassian ecosystem to get those. The integrations with stuff like Jira and Confluence are solid of course.
The features is does have are well implemented I feel. For example, the PR review UI is great. It is almost as good as GitHub’s and worlds better than GitLab’s. It has great access control that is probably a better fit for enterprise environments than the competition (another area where GitLab is lacking IME).
BitBucket added CI/CD. I’ve used it only for one project. It got the job done, but was worse than the others.
PM for Bitbucket pipelines here, my team of ~20 owns that feature E2W, would genuinely love to chat, share some stuff we're working on, and get feedback/thoughts.
Ping me if you're open to chatting emunday@atlassian.com
We use Bitbucket Cloud. About 250 repositories, 50-ish with CI/CD functionality. It is sloooow. In 2022 there were more than a few outages. Very annoying. And this year so far I had issues onboarding a new colleague due to invitation emails not being sent out.
Other than that it's cheap by itself, but count in developer hours spent just waiting, and it's suddenly not so cheap after all.
PM for Bitbucket pipelines here, my team of ~20 owns that feature E2W, would genuinely love to chat, share some stuff we're working on, and get feedback/thoughts.
Ping me if you're open to chatting emunday@atlassian.com
PM for Bitbucket pipelines here, my team of ~20 owns that feature E2W, would genuinely love to chat, share some stuff we're working on, and get feedback/thoughts.
Ping me if you're open to chatting emunday@atlassian.com