I love BitBucket and I'm using it for many repos but page opening or code view are unfortunately loading slowly.
I don't think it's from my internet speed or the cache.
How are your experiences?
Do you see any slowness?
It is still slow! The current slowness is frustrating - this breaks any sense of efficient work flow! Atlassian, whats our target with a saas build environment?
Current log entry:
> Cache "docker": Downloaded 250.9 MiB in 179 seconds
250 MB in 3 Minutes? Do I live in the 21th century? For a !!CACHED!! image? Maybe we have to change the build environment...
Been forced to use bitbucket for two years now, in comparison to using github for the better part of a decade - bitbucket has a LONG way to go to get anywhere close.
Over the past week or more, ALL merges take several minutes to complete, once upon a time longer than 10 seconds was weird. Usually negligible and seems dismal but those minutes were important to me and the client when on emergency work at 3am for international clients. I thought it was an intermittent issue but there has been no change on any day no matter the hour :\
Trust atlassian to call it a feature though: https://bitbucket.status.atlassian.com/incidents/8nbqbyxl2t03
Merges still incredibly slow, there has been no noticeable improvement over the past 7 days. I believe it may actually be slower than the last time I updated this post.
Will swap a 4/10 for an explanation or at least an informed response of whether or not this will be the new normal of "how long a merge will take".
Now moving several hundred repositories to GitHub.
Weeping in agony, showing symptoms of RSI.
They've posted this blog entry: https://bitbucket.org/blog/encountering-some-turbulence-on-bitbuckets-journey-to-a-new-platform
It acknowledges merges are slower than they used to be, but their solution appears to be updating the UI to make it clear what is happening rather than making it faster...
We're also now looking to move our code away from BitBucket and into GitHub.
The bells and whistles that go along with the whole Atlassian ecosystem just aren't worth the 5+ minutes every commit/merge/push seems to take.
For our needs, it only costs us 1$ more per user (~30 devs/users) to switch to GitHub. It's a no-brainer, really.
@Reece Alexander good luck on the migration, sir!
I get the plan: the performance of bitbucket will go up, if enough users leave ;)
Seriously, showing in the UI that a merge takes longer and is processed in the background is NO solution.
It is annoying, you get error messages on reload, and it breaks the workflow...
We had cases where an approval was done during a long "sync merge" which invalidated then the approval...
Please fix it.
BTW: with every "improvement" on Confluence, it also gets worse ... you might wanna rethink your improvement strategy...
I meant in fairness to the remediation they have made, merges no longer take several minutes. I'm not one to hold a grudge when an effort has been clearly made to improve the issue, I am a developer after all with plenty of perspectives - it's 30 seconds instead of 10minutes, that's good news no matter how you look at it.
Happy merging :)
fair enough :)
From my perspective leaving customers high and dry for months after rolling out a barely half-baked product update shows, to me, to what regard they hold their customers. The server update never even should have been released since it's a painfully obvious issue. Even then they should have rolled everything back until they could fix it. Instead they stayed the course (likely because of cost) and made their customers pay for their mistake.
So yeah, I'm happy the product we are paying for is once again useable, but do I trust them enough to believe it'll stay that way?
I've used Atlassian products for years now (BitBucket, Jira, Confluence) and this has always been an issue. It has gotten increasingly bad over the last years, every time they introduce a new UI it gets slower and more sluggish, to the point where it now takes 5-10 seconds to load a single issue. It's a terrible practice for a toolbox designed to optimize workflow.
I wouldn't hold my breath.
Performance has degraded terribly over the past 6 months and a fancy banner saying come back later isn't going to fix it.
Slow on all my repos and it doesn't matter the size of the PR. I get that merges can happen in the background, but that really interrupts your workflow when you're waiting on the merge to complete before going onto another task. E.g. we might really need that approved PR merged into develop before starting the next feature branch.
PR diff has been broken for ages. Okay, as a reviewer we all want smaller PRs, but Bitbucket should be able to handle PRs of any size. Recently we made wholesale changes to our apps package which touched 90% of our files. We ended up merging locally, reviewing the changes and then approving though bit bucket. We've lost confidence in the PR system with empty Diffs and files not appearing.
Seems GitHub or a local server is looking like a better solution.
Bitbucket is incredibly slow, by far the slowest git alternative there is. Pages take seconds to refresh and merge requests may take up to minutes (if they don't fail altogether).
All Atlassian frontends suffer from this. The only and best solution is to avoid it completely
WOW - BitBucket Team ... so SLOOOOOWWWWWW! I have a very fast internet connection. Other sites very fast,. But BitBucket.org is taking so long that I keep giving up. What the heck is going on? We have a significant corporate account with you. We may need to start thinking about other options if this continues.
What do you mean the Ad-Block? if you mean a browser or third-party Ad Blocker, well I am not using one. If you are referring to some sort of setting in Bitbucket then could you clarify. Thanks
However, the site has been much better for me recently so it isn't much of an issue now
That's ridiculous... 3 min to fetch the remote branch and I'm still waiting since 6-7 min to get my push (2 tiny commits) completed. Not to mention occasional bugs in Bamboo when it comes to deployment....
Sorry but if this doesn't change reasonably soon I'll convince my company to switch to some other alternative...
It literally took 8 minutes on the clock to merge a tiny 2 file pr. This is really not conducive to an efficient workflow. I understand that it's more efficient for Bitbucket to have things in a queue and have workers take care of things one at a time, but this system of queuing things up for eventual processing really only makes sense for non-time-sensitive tasks. Merging PRs can many times be very time sensitive and should not be relegated to a background task that will happen eventually. Can something please be done to fix this?
On some days, it's not bad. Today happens to be not so good, even this community page took a couple seconds of blank screen before showing. The repo page as of right now, still loading after waiting for 10 minutes.
I checked my internet speed and it's fine. JIRA on the other hand runs blazing fast for me.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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