Bitbucket from Australian-headquartered Atlassian offers source code management and version control.
$0
per month
GitHub
Score 9.0 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
$4
per month per user
GitLab
Score 8.9 out of 10
N/A
GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps teams across the complete DevSecOps lifecycle, from developing, securing, and deploying software. Differentiators, as described by Gitlab:
Simplicity: With GitLab, DevSecOps can…
From a cost standpoint, Bitbucket is the winner if you fall outside of the ability to use the GitHub and Gitlab free tiers. Both of those solutions have their own merits, but from a cost saving perspective Bitbucket is more than likely going to be the most effective option.
I think Gitlab and Bitbucket are very similar. I am very familiar with git commands so its easy for me to use both. But I would still prefer Gitlab since it has few additional features like send merge request, approvers etc.
Bitbucket was my repo host of choice when it came to private repos, but now that GitHub offers free private repos I’ll probably just use them. If you want to manage branch protection though you’ll need a Pro membership for GitHub whereas it was free with Bitbucket.
At the time of making the selection, Bitbucket offered free private repositories when no one else did. This was the primary motivator. With GitHub, you can now have free private repositories on personal accounts, but organizations must still pay for private accounts. Overall Git…
Of the three, we mostly use Gitlab the most. I don't know why as I was not part of the selection process. But if I'm to guess, this is an organization preference. Our company uses Bitbucket the most, while our partners either use Gitlab the most and sometimes ButBucket. But if …
We did select Bitbucket for a bit, but then we eventually moved away from using JIRA to different tools and as a result, it made more sense to move our source code to GitHub since it provides more features and is just much easier to use as everyone already knows how to use GitHu…
Bitbucket is good for private repositories and reliable CI/CD integration but it's getting behind GitHub which every day has more and more integrations and which in my opinion has a larger customer group. Gitlab also offers some good support for private repositories but the …
GitHub is a good repository to store and share code files. But GitHub is open to the community and public. But keeping the research codes private before publication is possible in Bitbucket.
Gitlab provides lesser features compared to GitHub. Gitlab/GitHub are both from a different company (Atlassian), which makes it tough to interrelate projects with other task management tools offered by Atlassian.
Bitbucket integrates with Confluence and Jira more easily than GitHub, which was a plus for us, given that we already used those tools extensively. Additionally, the pricing structure for Bitbucket makes it more affordable for our organization, which is especially important, …
Gitlab: Gitlab has a more robust code management and review system, but does not have any automated deployments so additional tools (such as Jenkins) would be required.
Visual Studio Team System (Azure Dev Ops) - VSTS is a better overall platform, since it provides a more robust …
1. GitHub is open source and also many security vulnerabilities because it is open source. That's one of the main reasons we chose BitBucket. 2. BitBucket integrates natively with other Atlassian tools without any custom configurations.
For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more …
When GitHub was acquired by Microsoft my previous organization had concerns about paywalls and additional restrictions that might be placed on the projects. We had made a move to Bitbucket as a result. The acquisition didn't seem to have any implications on the overall …
Bitbucket is perfect for our business because it allows us to work on private projects and integrate seamlessly with our existing tools. They also provide a nice app called Sourcetree to help developers work on git environments without experience with git command-line …
I have used GitLab and GitHub in the past. While GitLab is good if you are finding an open source solution for your code management and GitHub is good for the open source contribution, Bitbucket is an ideal choice to build an enterprise level product. The ecosystem that Jira …
I have used GitHub and GitLab before working on Bitbucket. There is no huge reason to choose Bitbucket over others. The only thing I like more about Bitbucket is security and user interface!
Verified User
Employee
Chose Bitbucket
The main reason why we choose Bitbucket is because they provide a secure way to save the code using private repositories. The Access control is easy to setup too
All 3 software works well for development and source code control, but for sure Bitbucket is the easiest to be set up and be deployed among the team. The integration with JIRA makes this a powerful tool against coding-only applications. However, for open source, it would be …
Bitbucket uses Git as a client which is more advanced with lots of features for source code management tool. It is very easy to scale horizontally as per our needs, and recent new features like adding multiple file systems keep Bitbucket more useful. Due to multiple file …
Bitbucket provides more features to version control and mange project sources. Build, test and deploy with integrated CI/CD. Benefit from configuration as code and fast feedback loops. Approve code review more efficiently with pull requests. Create a merge checklist with …
Bitbucket was inherited from an acquisition and not used by choice. The acquired company chose Bitbucket because - at the time - they were the market leader for private source code repositories and the team was already using JIRA.
Gitlab is the main competitor and they also have CI / CD capabilities, and also issue tracking, wiki. Gitlab supports static website hosting but does not offer dynamic Jekyll RoR server-side processing. The main advantage of Gitlab is that it offers private repositories for …
We maintain both GitHub and Bitbucket accounts but migrated our active private repositories to GitHub when private repository quota limits were eased. Our shop is primarily focused on open-source development and as such our team members' philosophies are generally in alignment …
While I think all of the main platforms provide the same core functionality (a cloud-based version control system), Github provides the most commonly used tools across different organizations. I think Bitbucket is very useful to blend with Jira, and Gitlab provides a little …
While I don't have very much experience with these 2 solutions, they're two of the most popular alternatives to GitHub. Bitbucket is from Atlassian, which may make sense for a team that is already using other Atlassian tools like Jira, Confluence, and Trello, as their …
I use Bitbucket exclusively at work and I prefer the UI and user experience of GitHub more. Bitbucket is a bit more barebones in its features. It doesn't have the nice-to-have bells and whistles that GitHub has. But it was first to market with free private repos so many chose …
GitHub isn't the primary repository management tool that we use. It is a good tool and is well suited for certain types of teams. It has many great tools built-in and is easy to use. But, we primarily use Bitbucket and are moving over to Azure DevOps. So, we didn't "select" …
Gitlab is my personal preference for source control, primarily because of the fact that it is open-source, and that it has great CI tools integrated directly into the service. However, GitHub is probably the leader with respect to enterprise offerings. GitHub has many more …
GitHub is at least as good as Bitbucket, if not a little more refined. GitHub is hands-down better than TFS. If you are using TFS, you really need to move to a modern source control system. The newer Azure DevOps Server has a decent Git offering, but the UX is incredibly …
GitHub is the de-facto solution for version control and code storage. Our team prefers it over other options like Bitbucket for its feature-completeness.
Github is the clear industry leader in collaborative software development -- we use it because it has superior tooling, integrations with third parties, and hosts a lot of the open source code that we use every day. Bitbucket is a better fit for organizations that are deeply …
One biggest reason is that GitHub is popular and used by many so it is easy to get contributions this also means that most people are already familiar with using GitHub. GitLab does offer more features and has more rich pipelines with the free repository as well but GitHub is …
GitHub is primarily targeted at developers and open-source communities, while Bitbucket is geared more towards small- to medium-sized businesses. GitHub has a free plan for open-source projects, while Bitbucket charges a fee for private repositories. For organizations with …
Verified User
Engineer
Chose GitHub
GitHub compared to GitLab and Bitbucket seems to have an easier and nice to use interface. This is mainly due to the fact that GitHub is the No1 choice for most of the Open Source projects. Developers out there are already famaliar to it's UX/UI and use it every day.
Another …
Verified User
Consultant
Chose GitHub
GitHub is the best platform to manage your source code. You can manage your CI/CD with different cloud service provider platforms and different languages. You can also create GHE for a number of organizations and repositories. Learning GitHub is easy and simple and supports …
GitHub stacks up against all of its competitors due to its ease of use and great UI that tops the all. I selected GitHub considering its popularity greater developer community. GitHub also provides Student Developer Pack that we can use to enhance our knowledge and get up to …
Verified User
Team Lead
Chose GitHub
Along with Github, I've used Bitbucket and Gitlab. Bitbucket integrates with FishEye, which allows you to institute Code Reviews and create a viable merge process. Gitlab offers similar built in tools. With Github, I'm not aware of any similar features, but this is likely due …
GitHub gives support for open-source applications. I think it has an easier and more reliable interface compared to other products on the market. You are able to expose your work via GitHub so that it can be used as a proof of your work to your current employer or future …
They're not listed here, but we've used Deltanji as well which is more suited for Intersystems specific products. But GitHub is far more modernized and can handle anything, and code reviews are a breeze with built-in comparison tools.
All these tools implement the Git and version control tools. But GitHub I personally like it more because the easy options available in GitHub is not present in any other version control tool. Like cherry pick, pull request.
GitLab is a self-hosted solution when compared with GitHub, but it has all the feature GitLab have. Overall this use case is the same, but I you do not want to store your code on the GitHub server, it is the best solution. Easily manageable but bound to resource restriction. …
Other solutions were studied, however GitHub being a SaaS solution causes security issues whithin many organizations. Bitbucket on the other hand can be installed and maintained however it must require licensing purchases. Although GitLab free version doesn't provide a lot of …
Although GitLab lacks some indexing service but it is well suited for big enterprises users for version control and ci/ cd pipeline. The user interface of GitHub is much better than GitLab. The search functionality of GitLab is far better than GitHub along multiple projects. …
We are coming from Bitbucket, and we switch to Gitlab to improve the source code management and the reading, which is better on Gitlab. The Merge request flow is also better than Bitbucket. This allows us to use Gitlab CI, which is well-integrated. Compared to GitHub, it is …
vs. AWS CodeCommit: As an AWS-centered organization, our teams have used AWS CodeCommit, the AWS native services that competes against GitLab. GitLab stacks better than CodeCommit even for development and CI/CD in the AWS ecosystem. It is more user-friendly, better version …
Actually there is no big difference between them it was a choice by our architects and i think its more professional tool than GitHub that is community
If you want a comprehensive platform with built-in CI/CD and deployment flexibility, GitLab might be your choice. If you prefer a broader ecosystem and a vibrant developer community, GitHub could be a good fit.
GitLab's online IDE and code modification is much better compared to Stash. While pricier than Bitbucket, Gitlab also provides CI CD configuration better than BB.
For small projects or companies that do work on a few only code repositories selecting one of the git code hosting services like GitLab, GitHub, Bitbicket etc does not make a big difference.
But, if you are on a code development company that handles too many repositories and …
GitLab has a open-source community and great documentation that provides support resources and community contributions. AWS CodeCommit is used for integration with other AWS services in the AWS ecosystem and also have a low community and support compared to GitLab hence …
It was a management decision to use GitLab over other tools. It integrates well with RBAC using Terraform. Runners are easy to setup. Almost all the features the organization used before are available in GitLab.
Software delivery is the key objective and GitLab made it much easier to hit the group quickly. It worked well with automation, and integrations with other SDLC tools used in the Organization and it is really easy to use. It's widely adopted and has the power to deliver what we …
Gitlab provided on par functionality and it provided a good option for us to self host which is very important for our business. We think the business continuity story is more solid with Gitlab.
GitLab is easily the preferred tool when it comes to versioning and source control. With other tools the UI often feels outdated and clunky leading to inefficiency and confusion. With some of the sleeker tools such as GitKraken, while the aesthetic is pleasing, the experience …
GitLab is easy to access either from Linux or Windows tools. Better control from CMS or Linus shell. Better & Easy understanding of UIs even for freshers. Fast CLI executions & Better support forums in case of issues.
More developer & collaborators friendly ui and features. Gitlab provides user to have Private repository. Lots of third party integration which work smooth.