I rate BitBucket seven out of 10. If you're considering BitBucket, do your research and make sure it's the product for you. There are several options out there.

For average IT organizations, depending on the needs and if the development is not very aggressive, Bitbucket is a tool that can match the organization's needs because the load is not much. We have Jenkins as a service, and all the integration is already available, so based on the organization's needs, Bitbucket is quite stable and less expensive.

I rate Bitbucket an eight out of ten.

Overall, I would rate it ten out of ten.

The product is predominantly used in the IT sector.

Bitbucket's collaboration is based on Git, so anyone can create codes with the same repositories. The collaboration process of Bitbucket is good, but there are a lot of limitations with respect to the functionalities, especially when we look at Bitbucket's competitors like GitHub or GitLab. Bitbucket is not at the level of GitHub or GitLab. Bitbucket is more for entry-level teams who don't want to get into security or the pipeline part of their product. For an entry-level team, Bitbucket is good.

In terms of the CI/CD pipeline, though Bitbucket has a pipeline, it is not so strong. The major advantage of Bitbucket is on the price front since its competitors offer tools at a very high cost. The products from competitors are offered at costs that are five times more than the price of Bitbucket. With Bitbucket, the pricing is minimal, and you get many functionalities.

Code review is not so solid in Bitbucket, so you can do only a limited set of activities inside Bitbucket. The pull requests part in the tool is actually good. I cannot see any standard features available in the tool, but it offers normal functionalities. Bitbucket has a lot of limitations in the reviewing part.

Bitbucket integration streamlines workflows since it has integrated with a lot of CIs. The tool also works with an open DevOps approach, though there are no ready-made or predefined plugins available, which allows you to just plug and integrate with the CI server. You can also go with webhooks or APIs as they give the diversity feature, allowing you to play with multiple products, after which you need not switch between products just for the sake of integrations.

Bitbucket handles large repositories or projects since it has Git LFS, so if we have a large file system, then it seamlessly integrates. The problem comes with the tool's memory-related capabilities since if you go with its premium plan, then it is good, but if not, then on a monthly basis, you need to renew your space, which can be a slight headache for a customer.

For an entry-level team in a company, Bitbucket is a good option. If there are people who want some advanced tool for version controlling of systems with CI/CD integrations, then they need to look at other options.

I rate the tool a seven to eight out of ten.

Scalability-wise, I rate the solution a nine out of ten.

Bitbucket is user-friendly and easy to configure. I would rate it a nine out of ten. 

I would have given Atlassian a nine out of 10, but because of the technical support issues and pricing, I would give them a seven out of 10 rating. I wouldn't even complain about the cost but they really need to improve their support model. 

This is a great tool that can help a lot to manage code between the environment, and merge codes and is highly stable.

I rate Bitbucket a nine out of ten.

I would rate Bitbucket a nine out of ten.

Learning to use Bitbucket, especially for beginners, is quite easy. In my experience spanning over twelve years in the field, most companies rely on Git for version control, and Bitbucket is just one of the platforms built on Git technology. The commands and client tools are the same: Bitbucket, GitHub, or GitLab. This uniformity makes it straightforward for beginners to adopt and use Bitbucket or any Git-based tool without facing significant challenges.

I recommend Bitbucket for version control features. It is a good tool suitable for long-term use. It's straightforward to adapt to, with user-friendly features and a convenient UI. 

I rate it an eight out of ten.

I rate Bitbucket an eight out of ten.

On a scale from one to ten, where one is the worst and ten is the best, I would rate this product as an eight. I love this product, so actually eight may actually not be good enough for the rating. On the other hand, there is a lot that could be incorporated or improved.

I rate Bitbucket a ten out of ten. I advise others to experiment with integrating the product with other vendors for deployment.

I recommend Bitbucket to others. I rate the overall solution a nine out of ten. 

I rate BitBucket eight out of 10. Bitbucket is an excellent product. Atlassian will move to the cloud, so the on-prem version may be phased out. You have to be careful when choosing this product. There will be a cloud version available, so it's better if you go with the cloud version of Bitbucket.

Bitbucket lets me create new projects in a few clicks and check out files in a seamless and integrated manner. It's also great for Linux users, including SourceTree running on Ubuntu, and for organizations that use Jira heavily. I would rate Bitbucket as eight out of ten.

Most providers provide scalable solutions, so that has not been something I've been concerned about. I'll know how to deal with it if I ever hit a hard limit. Likewise, hosting is not a big challenge. What concerns me is the service's features, whether it's BitBucket or GitHub. Similarly, I would be more concerned with creating the build pipeline, how well it's engineered, and supporting other platforms. For example, having the Mac OS or the iOS build tools available. A building environment is what I look for. And as long as the core repositories are working, scalability is my last concern.

When choosing a service, it's not just about the service alone but what the organization has adopted because that greatly determines what we choose. Otherwise, we would be competing with what the market provides in the future. 90% of future challenges would be because we poorly chose a tool.

I rate Bitbucket a six out of ten.

It's very easy to use and a nice tool to manage. And I think the first implementation or the configuration is very important so that teams could work with that.

I rate it nine out of ten.

I would rate the solution a nine out of ten since its an awesome tool for source control and versioning. 

Bitbucket is worth the investment. Overall, I would rate the solution a nine out of ten. I recommend using the solution.

I recommend the solution to those who plan to use it.

I haven't explored the entire solution yet, so it would be best for me to rate the solution a ten out of ten after I do a deep dive into the product's capabilities. I rate the overall solution an eight to nine out of ten.

I would rate Bitbucket a nine out of ten.

I would recommend this solution to others.

I rate Bitbucket an eight out of ten.

I rate Bitbucket an eight out of ten.

I use the latest version of Bitbucket. I would recommend users to use Bitbucket if they have the budget.

Overall, I rate Bitbucket a nine out of ten.

For general company usage, Bitbucket should fit the purpose. If you have a larger team you better look for other options. For a more complete solution for your CICD, I would recommend GitHub.

I rate Bitbucket a seven out of ten.

I rate the solution an eight out of ten. 

I would rate Bitbucket a nine out of ten.

One person can maintain the solution.

This is a good solution that has many features.

I rate Bitbucket a nine out of ten.

I rate Bitbucket a seven out of ten.

I rate Bitbucket eight out of 10. 

I would advise getting some Git training.  Something like 85% of all developers use Git. So it's like the defacto standard for source control.  Bitbucket is a brand of Git that has some nice features on top of the core functionality.

The biggest lesson learned was, we should've done a little bit more training for the developers. It was very informal and should've probably been more formal, not necessarily sending everybody to university or a class, but a little more hand-holding.

I would rate it an eight out of ten. I give it this rating because there was the integration with the other tools.

Overall, I would rate the solution an eight out of ten. 

I would definitely recommend using the solution because one of the great features of Bitbucket is its compatibility with other solutions like Atlassian and others. I highly recommend it.

Before implementing Bitbucket, people should be clear on the tools they will have to adopt based on their needs. It goes well with other Atlassian solutions like Jira or Bamboo, but integration with other third-party solutions is more complex. I would give Bitbucket a rating of nine out of ten.

I rate BitBucket eight out of 10. It's accessible to beginners. They can start by layering BitBucket and move on to other tools.

Bitbucket is definitely a tool to consider if somebody is still on CVS. It is a great tool and well integrated with Bamboo. Both Bitbucket and Bamboo are made by the same company, and the latter is there to connect the dots between the code and releases in production.

My advice to others would be that, if they are looking for a stable on-premises solution, Bitbucket is the obvious choice. They can even use it if they are looking for a cloud solution, but we have a restriction that we have to run it on-premises. Therefore I think it's the smallest, best solution for us. 

I think it's worth paying for the extra features because otherwise you end up spending a lot of time configuring open source products. 

On a scale from one to 10, I rate Bitbucket a nine.

This solution is good and it covers all our needs. Periodically, I receive announcements from Atlassian, mostly concerning the security features. They are fixing the newly discovered vulnerabilities and also, there are some other improvements in the features. Normally, I am not affected by the new features because we don't require them.

My advice is to start using this solution because it works very well and we are very satisfied with the functionality. If somebody knows how to configure git for libraries then they can implement Bitbucket as well.

I would rate this solution a ten out of ten.

I'm working as a software engineer.

My company has four Bitbucket users.

My rating for Bitbucket is nine out of ten.

I recommend the tool to others. One company even consulted with me, and I told that company to focus on Bitbucket.

My company is a Bitbucket user. There's no partnership currently.

I can definitely recommend using Bitbucket and would rate them a nine out of ten.

I rate this solution a seven out of ten. We want people to use Jira for an integrated approach between Jira and all the products. Regarding advice, If you want an enterprise-class product, I first recommend Jira, and then I would recommend Bitbucket.

We use the cloud deployment model.

We use the solution pretty extensively, but it depends on the client and the project.

I'd suggest those considering implementing the solution try all the functionalities in the trial period. That way you can decide if it will work for your projects.

I'd rate the solution eight out of ten.

If someone is going to migrate their own code from an SCM to Bitbucket, it could take a lot of time if your code is a bit older. That means that you have larger number of divisions, so it could really take much more time for transferring that to Bitbucket. Otherwise, there's no issue migrating. If it's something that will go directly into Bitbucket, it's just a one-step process.

When it comes to the migration process, because most developers are used to working on other tools, migrating them to Bitbucket takes some time. If Bitbucket had its own migration tool or utility that could be used directly to transfer your SCMs from the older system to Bitbucket, it would have been better. We had to figure out some way or other to do that. If they would have provided something like that, that would have been a plus point.

Overall, it's quite good. It gives you lots of flexibility to use it. It follows all of the site framework. The best practice is that you are required to have your code reviewed before it's committed. Also, there are many layers of permissions that you can apply to a repository.