Bitbucket Pricing Overview

Does the basic work delightfully. This includes basic Version control system, Pull requests, sync with target branch. The pull request section is definitely helpful as you get multiple options such as merge conflicts and the ability to ask the developer for any kind of changes which otherwise would is a very tedious task.

The main idea for dislike is the inability for the purpose of CICD pipelines as they are not feature-rich. One of the main points of disapproval will be that I cannot replicate what I think in the CICD pipelines. An example would be that the first step in the pipeline cannot be a manual step so this is a limitation for the Advocate side and which was a negative impact on my case.

The problem that we solve is the VCS system in our organization. Bitbucket maintains all our code, and Bitbucket also supports all the necessary CICD pipelines. Also, Atlassian is brilliant to include bitbucket as a discounted product if you buy Jira and Confluence. So it helps us in the cost-effective case too. Benefits will be cost effective ness, single solution for all the code, CICD needs.

I use the GitHub function to compare a dataset master to an updated file. This gets me a list of all the changes between the two files, so I can just post the changes. Then the system allows me to update the master file with the changes. I then repeat the process every week from March to October. We have 2300-2400 eContracts memberships for 0ver 66 different contract types with over 200 different school entities to keep track of. Bitbucket coding using GitHub saves 90% of the time involved (reduces several hours to several days time determining the changes to only 30 -120 minutes posting the changes only). A massive amount of time saved, as the system is not able to be automated.

I do not have a problem with this software.

Managing contract memberships and discounts for fee-based course offerings.

Bitbucket is an ideal solution for many small companies that are looking for version control and somewhere to host their files. Some of the items we like best at our company are the version control, the issue previews, the file system hosting, and the overall pricing model. Many other competitors charge for private repositories but bitbucket actually bases their prices on users, which makes it super affordable for smaller teams. Bitbucket also does a great job allowing my manager to review my code before committing it to the branch. Which means better code review and a better quality product.

Bitbucket also has some downfalls because it doesn't have a massive community behind it like some of their competitors. Additionally, their desktop application "SourceTree" is full of bugs which can make interacting with bitbucket a pain for new developers that aren't used to working within terminal.

We originally got bitbucket just for storing files for sharing and to be able to work on the same project with similar files. One of the great features we realized are are the great Version Control it offers.

It is great to be able to do the code review within Bitbucket. Bitbucket work perfectly with all the other Atlasian products. The plugin collection is pretty good. And the quality of the plug is great too. It does offer a great interaction with Jenkins to execute CI/CD.

We don't like the fact that Bitbucket Cloud and Server or so much different. We would have though that the later is the same has «bitbucket.org», but on premise. It is not, it is a different product with different set of Api. The plugin market is great, but the price to add some basic functionality is something ridiculous.

We have move from different set of tool (gitolite, fisheye, crucible) to a single product Bitbucket. It has reduce our product costs and maintenances fees.

A great alternative to Github. Bitbucket provides privates for free. If your moving from github, easy import of repos also available. Bitbucket is needed when development is collaborative or in team. Bitbucket provides all features of Github with better APIs and better prices. Best suited for small teams or individuals.

Generally not suited for open source projects. Github is best for open source. The website is slow to load maybe due to high GUI. Pricing for big teams is high though for small teams it is free of cost. Sometimes confusing if you have shifted from Github.

For version control management Bitbucket has been used. Bitbucket is best since access to the repo must be private(authorized). Benefits: Free private repos helpful in version control management for teams. ease of integration with Github

* I believe it achieves the right balance for the Freemium model in the git SaaS world. * Integrates well with Jira, allowing tracking of bug/fix commits within Jira issues * They are the developers of SourceTree which is one of the most capable git desktop clients (at least on the mac) * The ability to review and comment on commits in the web interface

* Even after a recent redesign, the UI is cluttered and confused

We found Bitbucket very capable and when we first started out, it was important to us that their pricing was startup friendly while still allowing us to create private repositories right off the bat without paying (unlike github) We needed a capable git SaaS that allowed us to create private repositories without having to pay a lot because source code repositories are fundamental infrastructure that you want to stress test for a while before committing to it. Paying up front (like for github) creates a powerful disincentive to leave even if the service doesn't turn out to be optimal. I also feel that Bitbucket seems to charge for the right features. As an example, they started charging as soon as we exceeded 5 users. This is very startup friendly - we were strapped for cash early on but a bigger team is a good indicator of financial health and is a good time to start charging for access.

Easy to start with. Later once we scale, I think it's easy to scale our business.

The prices should be users in groups, like for first five users some price and rest different price

team meetings in different remote places

The business model behind BitBucket certainly helps small companies with small development groups: compared to other systems, Atlassian focuses on charging the users with a price only for bigger teams, while smaller ones gets the software for free, with unlimited repositories available right away.

BitBucket is great at what it does, but it is not as complete as GitHub: you will most probably need to purchase other softwares to efficiently keep track of the bugs, perform code reviews and so on. It is surely a business model, but it makes the software feeling incomplete. It's a great tools, and I would suggest to use it if you need a private git repository

In almost every company in which I have been, BitBucket was the choice for the Android team: we usually are in small teams with a lot of repos, so that BitBucket provides the best solution for free, helping us with the versioning and the integrations (the Slack one is certainly one of those I love the most).