21–30 of 42 posts
The 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)
I'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?
Earlier quoted context omitted.
Have you noticed any drawbacks to using Gitlab over Bitbucket/Github?
Not OP, but as a majority user of Gitlab the only downside is integrations. By that I specifically mean Codeship. It's just not considered a first class citizen to some yet, which is unfortunate.
The 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)
I actually prefer bitbucket cloud to github. The pull request workflow in particular is a lot cleaner. Currently ditching both for gitlab tho.
Earlier quoted context omitted.
Have you noticed any drawbacks to using Gitlab over Bitbucket/Github?
Not OP, but as a majority user of Gitlab the only downside is integrations. By that I specifically mean Codeship. It's just not considered a first class citizen to some yet, which is unfortunate.
In the meantime, is there anything that we can improve in GitLab CI to make your switch possible?
The 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)
Earlier quoted context omitted.
Not OP, but as a majority user of Gitlab the only downside is integrations. By that I specifically mean Codeship. It's just not considered a first class citizen to some yet, which is unfortunate.
For us at Codeship, it has nothing to do with not taking GitLab seriously, not treating them as first-class citizen, etc. We'll add GitLab support, hopefully, sooner than later. There are simply other feature requests that are more important for existing customers that are already using Codeship.
Earlier quoted context omitted.
Not OP, but as a majority user of Gitlab the only downside is integrations. By that I specifically mean Codeship. It's just not considered a first class citizen to some yet, which is unfortunate.
Codeship support might happen, see https://news.ycombinator.com/item?id=12697135 In the meantime, is there anything that we can improve in GitLab CI to make your switch possible?
Appreciate the response either way.
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).
Earlier quoted context omitted.
Codeship support might happen, see https://news.ycombinator.com/item?id=12697135 In the meantime, is there anything that we can improve in GitLab CI to make your switch possible?
To be completely honest - probably nothing. This is a legacy issue on our end, not yours. I haven't even taken the time to explore migrating our GH/Codeship builds to GL CI. We essentially mirror our repos amongst both offerings at the moment, running builds via Codeship until either they support GL and we can drop GH, or we get the time to spend on a proper Codeship => GH CI migration and we can drop Codeship. Anyon…