* 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)
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...
Disclosure, I work for Atlassian, but not on either of these products.
The Bitbucket UI has improved over time but my real annoyance is the "Recent Activity" list is not wide enough and is not very configurable (ie filtering).
Also Bitbucket has sort of forgotten its Mercurial roots. Many Mercurial features have been added but it appears the Bitbucket UI does not show these features (for example Mercurial tracks moved files but Bitbucket does not show this).
The pipeline looks interesting but it is just a little too late for us since we are so heavily invested in Jenkins + Bash and will probably use Jenkins pipeline (Groovy) in the future. And if we do more opensource stuff it will probably be on Github so we will continue to use Travis. Also in all honesty I'm fairly sick of the whole YAML configure the world explosion... I actually miss XML but would prefer a scripting language over YAML (then again maybe I'm the only one who hates YAML).
Finally why is the Bitbucket blog so darn slow?
(I added this critique because I saw a Bitbucket PM floating around here).
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?
At the same time I understand bb needs to make money - hopefully they'll make enough to keep up the competition.
> I understand bb needs to make money
The only real downside at the moment is for public open source github is still the place everyone is expecting you to be. Its hard enough for small projects to be noticed on github, putting them somewhere else means nobody will ever see them just browsing. But for private or private-for-now projects gitlab seems to be the best fit for me currently.
We'd much prefer to use EFS but I understand that it's not supported, since there's no way to set `lookupcache=positive` (git push might update the ref to an object which may not be immediately available across all NFS clients & they would cache that the object doesn't exist unless this is set)[0]
[0]: https://docs.gitlab.com/ee/administration/high_availability/...
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.
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...
Sten
Much as I like Bitbucket I think either hosting my own CI and CD infrastructure on a cheap VPS or using gitlab is the way to go.