Why would you ever willingly choose bitbucket over Gitlab? Does Bitbucket offer syntax highlighting when reviewing code changes yet? When we used it (before migrating to Gitlab) you had to install a third party browser extension. What a joke. Edit: nope, not yet: https://jira.atlassian.com/browse/BCLOUD-8673 . Opened in 2014.
How to Migrate a Git Repository from GitHub to Bitbucket
31–40 of 53 posts
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#32Why would you ever willingly choose bitbucket over Gitlab? Does Bitbucket offer syntax highlighting when reviewing code changes yet? When we used it (before migrating to Gitlab) you had to install a third party browser extension. What a joke. Edit: nope, not yet: https://jira.atlassian.com/browse/BCLOUD-8673 . Opened in 2014.
Because Bitbucket Server had syntax highlighting probably for more than a decade now.
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#33Migrating to Bitbucket: Uh....
I don't really see any way in which Bitbucket is better than Github. Or, frankly, any other alternative. It exists due to inertia and/or to serve people irrevocably emeshed in the Atlassian ecosystem. I can understand why you might not have switched away yet, but switching to it?
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#34Re: How to Migrate a Git Repository from GitHub to Bitbucket
#35Bitbucket is horribly antiquated (along with all Atlasssian software IMO), why not go to GitLab - it's code management, merges request workflows and discussions are excellent for peer review and the CI/CD is fantastic.
We just switched from GitLab to GitHub because the CI is horrible and they changed the pricing to a very bad option in our case. Without adding features we use we would've had to pay four times the money. The CI just sucks, it's very flaky and just outright unstable sometimes. The configuration is pure horror. It takes ages to implement simple stuff. In two years I didn't get sonarcloud annotations on our damn pull r…
Did you self-host? How did you deploy it?
Gitlab CI has been "the best"(tm) self-hosted CI solution I've used.
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#36Earlier quoted context omitted.
GL is pretty great at the following: cost, permissions and CICD.
The pricing has changed recently, grandfathered in organisations have reasonable pricing (relative to GitHub) but the pricing for new organisations is much more expensive than GitHub. You can compare GitLab on features, but if you want to use those features the pricing is not comparable (GitLab's $100/user/m vs. GitHub's $21/user/m). https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-...
GitLab Premium is ($19/month + runners + [optional] self hosting) vs ($21/month + possibly leaking your code/secrets in copilot).
And, in my opinion, GitLab CI has a much better feature set and integration than GitHub's. You have so much opportunity to optimize the performance of your runners just off the bat. It's quite amazing especially for people with larger repos (ex: monorepo companies).
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#37Earlier quoted context omitted.
What's unethical about GitHub?
I was referring to the current controversy with licensing of co-pilot code and them serving ICE customers.
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#38Bitbucket is horribly antiquated (along with all Atlasssian software IMO), why not go to GitLab - it's code management, merges request workflows and discussions are excellent for peer review and the CI/CD is fantastic.
I've found the ability to tie tickets to commits really nice. And it's CI is good enough.
Not saying it's better than other solutions use what makes sense for you.
Re: How to Migrate a Git Repository from GitHub to Bitbucket
#39Bitbucket is horribly antiquated (along with all Atlasssian software IMO), why not go to GitLab - it's code management, merges request workflows and discussions are excellent for peer review and the CI/CD is fantastic.
We just switched from GitLab to GitHub because the CI is horrible and they changed the pricing to a very bad option in our case. Without adding features we use we would've had to pay four times the money. The CI just sucks, it's very flaky and just outright unstable sometimes. The configuration is pure horror. It takes ages to implement simple stuff. In two years I didn't get sonarcloud annotations on our damn pull r…
The new CI/CD pipeline editor also improves the getting started experience, shown in a demo workshop in the GitLab 14 community meetup: https://www.youtube.com/watch?v=mSspEk8efHE
Can you elaborate a bit more on the CI configuration problems you are running into? Thanks!