Bitbucket Reviews

The solution is used for web-development

The solution is good for cloud collaborative work. During the time I was working as a release manager, I could manage the tool request and the technical problems that occurred on the site of the development.

We can watch the newly implemented code. So it's quite nice to organize the teams to see what part of the work is done and what part of the code is already old or new. It is very good for that kind of management.

The scalability for the cloud version can be improved.

I have been using the solution for nine months.

It is a stable solution.

It is a scalable solution. The cloud version is not scalable. But if you pay for the premium version it is very scalable. Five users are using the solution at a time.

I have only taken demos for products before and did not use anything. It was mainly the license solution. I was searching in several websites, and all of them were talking good things about the Atlassian solution. So I decided to give it a try.

The initial setup was easy and quick.

I deployed the solution myself.

I did not pay for the license as I was using a corporate license. But I think the pricing is fair.

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.

Our primary use case is for change management more specifically software development. 

The most valuable thing we have found is the workloads are good in Jira and we are able to control the access.

I would like to see the security logs option on the tool directly. The current way to work with security logs is through an email protocol.

I have been using Bitbucket for the past year and a half.

The stability is good and we have not had any issues.

Bitbucket is scalable and we have seventy-five to ninety users.

The technical support that we have received has been very good.

Positive

I have been working with Github and the organization decided to go with Bitbucket.

We used in-house support with Bitbucket.

GitLab was the other option and I have not worked with it. I do not have a personal preference between GitHub and Bitbucket.

I would rate Bitbucket a nine out of ten.

We predominately use Bitbucket for continuous integration, as a repository for our code, and for various departments, such as analytics, web, and mobile.

Bitbucket could improve pipeline building and deployment. Our deployments are not using the Bitbucket. Deployments we are going through Azure DevOps, but the integration is happening in Bitbucket.

The repository and the access levels could improve.

I have used Bitbucket for approximately four years.

We have not had any issues with day-to-day usage of Bitbucket since we started using it.

We have not scaled Bitbucket that much to know the full range, but for what we use it for it has been good.

We have 10 to 20 users using this solution in our organization.

I have not needed to use the support team from Bitbucket.

The setup of Bitbucket is simple.

We have approximately 40 licenses for Bitbucket.

We did a benchmark before we chose our continuous integration environment. We found Bitbucket is the right tool for us at the start-up level. We conducted tests for Git, GitLab, and other solutions, but the decision we made was Bitbucket.

I rate Bitbucket an eight out of ten.

We use Bitbucket for version controlling our source code, and also CI/CD was utilizing Bitbucket pipelines. We have automated build pipelines, daily master build pipelines, and daily releases.

It nicely integrates with Atlassian Jira, making it easy to find relevant branches and PRs. We also have Teams integration for Atlassian products like Confluence.

It has a nice user experience to review PRs and provides great pipeline features, integrating well with other Atlassian products.

Bitbucket pipelines could be enhanced by adding scalability and caching for images. If we could get the cloud-native benefits to Bitbucket pipeline like in Tekton, it would be great.

I have used the solution for about two years.

The solution is stable.

Our main repository gets around 200 PRs per day, and this load has limited Bitbucket pipelines due to steep limitations.

Customer service is actually done by the R&D and Deployment team. I'm not really aware of those details.

Positive

We moved from Bitbucket to Tekton because our main repository gets two hundred PRs per day, which presented a load on Bitbucket pipelines with step limitations. Moreover, we do not have local image caching, resulting in frequent pulls from Azure Container Registry, leading to Azure's rate limits.

We compared Bitbucket with Tekton, noting the benefits and limitations of each.

I'd rate the solution eight out of ten.

We use the solution in every project as a source control management software to control the versioning of the code.

The tool's UI is better. 

I would like to see the tool's desktop version. 

The solution is stable. 

I would rate the product's scalability a nine out of ten. 

I have used GitLab and GitHub before and I find the solution to be more user-friendly. 

The tool's deployment is simple and we use the cloud version. 

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

We have a Bitbucket server internally, that we manage with our own IT team. We use the solution as a software control repository.

Bitbucket could improve search and indexing capabilities. There is only basic searching available. There is only the ability to index the main branch but not the subbranches. The search capabilities are dodgy.

In a future release, the way they manage the permission of the records in the solution could be better. They fit well if you're only running one or two projects. If you have a lot of projects and records, the current permission model is not flexible. You have a challenge if you want to provide permissions across all the projects to be the same. Additionally, if you want to have specific permission there are limitations. There requires a lot of redundant work to accomplish what we want.

I have been using Bitbucket for approximately six years.

Bitbucket has some initial stability issues because of our large team using the solution. However, this was later resolved.

I rate the stability of Bitbucket an eight out of ten.

We have approximately 300 to 400 users using this solution. Our whole organization uses it.

I rate the scalability of Bitbucket an eight out of ten.

I have not used the support from Bitbucket. However, my team has used the support. The support has been fine, they have not had any downtime.

I have used GitHub and it has more features than Bitbucket. Additionally, I have used GitLab.

GitHub is a more mature solution compared to Bitbucket. The search capability has improved in GitHub since they are integrated with Opensoft. You can create your workflow and actions and it becomes easier to do things. GitHub can help a lot. The only season why our organization didn't adopt it is because of the high pricing.

The initial setup of Bitbucket is straightforward. 

The initial setup was in-house. However, it is possible they had some assistance.

Bitbucket is a cost-effective solution. It is the cheapest in the market. It is lower than GitLab and GitHub.

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.

Bitbucket can be deployed on the cloud or on-premise.

We use Bitbucket to set up an end-to-end integration system.

We use Bitbucket for Jira, Confluence, and Jenkins and we have an automation pipeline. Whenever the coaching is done in Bitbucket we run an automation pipeline from the build, create installations, and tests all in one pipeline. It is done automatically. 

Bitbucket could improve its security. For example, the user access security could improve.

I have been using Bitbucket for approximately six years.

Bitbucket is stable. However, every one or two months it crashes, it depends on the usage. When Jira is down after a long weekend Bitbucket might not be working. There could be other reasons it is not working and not necessarily the solution's fault.

The scalability of Bitbucket is good.

We have a lot of developers working and we are moving the solution locally to the cloud next year. We plan to increase the usage of the solution.

I rate the support from Bitbucket a four out of five.

Positive

I have used CVS previously.

The initial setup of Bitbucket can be complex. It depends on what you are using it for. For example, when I was using Jenkins I had to set up a lot of scripts to link all the tasks together for it to run automatically.

I would recommend this solution to others.

I rate Bitbucket an eight out of ten.

Our company uses the solution for code management. 

It is easy to write code and store it in the central repository. 

Fine tuning for procedures and features related to analytics and code validation is needed. 

There are some issues in obtaining licenses.

I have been using the solution for two years. 

The solution is stable so I rate it a nine out of ten. 

The dynamic solution is definitely scalable and customizable to any need. 

Technical support is pretty helpful so I rate them an eight out of ten. 

Positive

The setup is simple with no issues. 

We implemented the solution in-house. 

Sometimes there are issues in obtaining licenses and the pricing could be improved.

I rate pricing a six out of ten. 

We did not evaluate other options. 

I rate the solution an eight out of ten.