Bitbucket Server Reviews

My major use case for Bitbucket Server is that it is a source code repository. We are using it to store our application source code, and we are tracking the check-in, check-out, and all the activities.

The biggest benefit I see from Bitbucket Server is that it is providing all the features which Git is providing. Bitbucket Server is using Git as a source code main tool, and it has all the features that any source code repository can provide. A plus point is that we can install it on-premises and manage it easily.

Using Bitbucket Server helps me easily track my code changes and where they belong, which saves a lot of time and effort. Without Bitbucket Server, it is very difficult to track the code and changes.

The integration with Jira helps me personally with project tracking because Bitbucket Server is a source code repository. We have our SDLC lifecycle in Jira. Every change or every feature request is created as a ticket in Jira, and this ticket is linked with Bitbucket Server repository. Any changes to the code linked to that feature will go to the repository, and we can track that this is the code changed by this feature.

There are certain features in Bitbucket Server that could be better or enhanced, which would make our life easier. One limitation is that we can control granular permissions, but there are some limitations on the granularity of the permissions. We cannot deny access at a branch level; there are some tricky areas, so Bitbucket Server should provide more flexible configuration for granular permissions.

I have been using Bitbucket Server for almost eight years.

Bitbucket Server is quite stable, and I did not see any performance issues.

Regarding the scalability of Bitbucket Server, to be honest, we don't have much requirement in terms of scalability because we have a very small user base, but I can say that Bitbucket Server is quite scalable because it is a server-side solution, and we can scale it vertically easily.

The support from Atlassian is actually good. Overall, I would rate it as good support from Atlassian.

If I had to rate the support between one and ten, I would give them nine points. I cut one point maybe because sometimes we are unable to find the solution easily; we have to dig too much, and sometimes the solution is there, but finding the right solution becomes difficult because there are so many things that create confusion.

Positive

I have worked with something similar to Bitbucket Server, specifically Team Foundation Server.

I have also worked on GitHub.

Bitbucket Server installation is a little bit complicated, and it requires vendor support most of the time.

The complication I face while installing Bitbucket Server is that because we are using it on-premises, when we upgrade Bitbucket Server or install it on a new server, it requires Java Virtual Machine, and sometimes the Java Virtual Machine compatibilities are a problem. There are also other configuration issues, such as when integrating with Jira, Bitbucket Server configuration requires SSL from the back end, so those complexities require troubleshooting and maintenance from our side.

Bitbucket Server license is affordable.

The comparison between Bitbucket Server and TFS depends on the requirements. If you have an Atlassian product suite, you should use Bitbucket Server because it easily integrates with other Atlassian products such as Jira, Bamboo, and Confluence, as well as Fisheye and Crucible. However, if you are not using Atlassian products, other solutions might be better.

I am working with Bitbucket Server today, and there is no issue.

I am not using the pull requests feature.

Bitbucket Server by itself is not very collaborative, but if I use Bitbucket Server with other products, such as Atlassian's other products, it will become collaborative.

We have an integration with Jira.

We are not using Git large file storage in Bitbucket Server.

The granular access settings in Bitbucket Server are quite granular. I can give access at the project level, repository level, or branch level also, which gives all the options.

We purchased Bitbucket Server through an integrator.

I would rate this product a nine out of ten overall.

We use Bitbucket Server for storing code.

It is a way to manage configuration items, keep track of code, commits, and pull requests.

The pull request feature in Bitbucket Server is necessary.

There are absolutely things that could be improved in collaboration features in Bitbucket Server, with respect to people who are not using it every day, such as managers who need to be able to approve things but don't use Bitbucket Server so often.

Collaboration could be improved as the main aspect.

I don't use Bitbucket Server myself, but we have developers who use it. We have used Bitbucket Server for at least seven or eight years.

Bitbucket Server has been working efficiently for us so far, and I would rate it an eight or nine for scalability.

Pricing for Bitbucket Server is always a consideration. Every system costs a lot of money. I don't recall the pricing schedule because the purchasing department keeps track of that.

It's probably slightly expensive, and the cost depends on what you compare it with.

We use Bitbucket Server in the company.

Since I'm not using Bitbucket Server every day, it's more my technicians, developers, and engineers using it. I would need to talk with them first.

We use Jira integration with Bitbucket Server, but I'm running out of time.

I would need to discuss the satisfaction with these integrations with my technical product owners because they are more involved in this than I am right now.

I believe installing Bitbucket Server is quite easy, but I'm not doing the installation or integration. I'm just working with other people who do that.

I couldn't provide points for technical support because I haven't been in contact with them much.

On a scale of 1-10, I rate Bitbucket Server an 8.

Bitbucket Server is used for private code management and source code management. It facilitates versioning, allowing us to maintain a master branch which reflects the code in production, and manage separate features being developed. It also integrates with Jenkins for compliance checks, coverage tests, and continuous integration and deployment.

Bitbucket Server excels as a versioning system, effectively managing branching and code integration. It provides flexibility, allowing teams to customize workflows according to their specific needs. We maintain a master branch for production and separate branches for different features, which makes it easier to manage code changes. 

Additionally, its integration with Jenkins pipelines for automating builds and performing various checks enhances its utility.

While Bitbucket Server performs well, the improvement lies not in the tool itself yet in the discipline of the team using it. The tool does not impose restrictions, allowing for flexibility in workflow management. There might be further integration ideas for continuous deployment.

I have been working with Bitbucket Server for over ten years.

We have an internal support team that handles potential issues with Bitbucket Server. If they encounter problems beyond their scope, they contact the vendor directly.

Positive

Before Bitbucket Server, we used various tools like Visual Studio, VCS, and Microsoft TeamSuite for project management and source code control.

As a technical team, we do not deal with licensing and pricing.

In the past, we have used solutions like GitHub, Visual Studio, VCS, and TeamSuite. GitHub compares closely with Bitbucket Server in terms of functions.

I recommend using Bitbucket Server for Java-based development due to its effective management features. However, for Microsoft projects, GitHub might provide better integration due to its ecosystem. 

Overall, I rate Bitbucket Server as eight out of ten due to its compelling features and flexibility.

The platform's most valuable features are the code reviews and the ability to add comments to the code. It also integrates well with SonarQube, which is a significant advantage. When you push your code for review, SonarQube adds its comments directly within Bitbucket, so you don't have to navigate to SonarQube separately. This integration helps maintain high coding standards and catch errors early, potentially reducing production issues.

Bitbucket can improve in several key areas to enhance its user experience and functionality. One significant area is the code review experience. Currently, the interface could benefit from a more sophisticated code viewing option. Introducing a code color theme similar to what is available in Integrated Development Environments (IDEs) like VS Code would greatly enhance readability during code reviews. It would allow for highlighting keywords, making scanning and comprehending code easier.

It provides several pipeline examples, but notable limitations exist, particularly regarding the number of pipeline minutes allocated to users. This constraint often forces users to rely on their on-premises servers instead of using Bitbucket Pipelines. Additionally, Bitbucket Pipelines currently do not offer any unique features that set them apart from other Continuous Integration/Continuous Deployment (CI/CD) solutions. Compared to alternatives such as GitHub Actions, Bitbucket Pipelines may appear less competitive due to its lack of distinctive functionality.

We've been using Bitbucket Server for a few years now.

We have around 40 to 50 Bitbucket Server users in our organization.

We recently faced an issue with the product. It took us two to three weeks of consistent follow-up to get the support team to address it, which they eventually resolved in about six to seven hours.

Initially, we worked with Gerrit, Google's code review system. Later, we migrated to Bitbucket. 

We mainly shifted to Bitbucket to move away from a self-hosted Gerrit server, which required a VPN for access. The platform, being globally available, is much more accessible and user-friendly. The shift was driven by the ease of use rather than concerns about ROI.

The initial setup process is straightforward. 

As for licensing, Bitbucket is one of the more affordable options, charging around $10 to $20 per user per month, cheaper than its competitors like GitHub and GitLab.

The solution's integration with Jira is excellent, making it highly effective for teams using both tools. It has certainly made things easier regarding accessibility and usability. 

Overall, I don't recommend Bitbucket. I would suggest alternatives like Gerrit or GitHub.

I rate it a five out of ten. 

We use the solution primarily to manage and version our code repositories. It integrates with our continuous integration and continuous deployment (CICD) processes. Specifically, we utilize the pipelines for deployment and code quality checks. This setup ensures that only code meeting our quality standards is deployed, preventing issues in production.

The platform has enhanced our organization by streamlining code management and review processes. Its features support efficient code reviews and maintain high code quality through integration with our CICD pipeline. It has led to more stable and reliable deployments, which improves overall productivity and code integrity.

The product's most valuable features include its code review interface and permission management system. 

The improvements in the product could be made to expand third-party integrations and enhance support for open-source projects.

I have been using Bitbucket Server intermittently for both personal and company repositories for approximately two to three years.

The product's stability is impressive. It has consistently performed well without major issues, providing a reliable code management and collaboration environment.

The product is highly scalable and effectively supports both small and large projects. Its ability to handle third-party integrations and accommodate growing codebases contributes to its scalability.

I have used other version control systems but switched to Bitbucket Server due to its robust integration with our existing tools and effective code review and permission management features.

The initial setup was straightforward, involving simple SSO login and password management. It did not present significant challenges and was manageable with minimal effort.

The setup was carried out in-house. 

The platform offers a free version for public repositories, which benefits open-source projects.

I evaluated other version control options.

Overall, the solution is a robust and reliable tool for code management. 

I rate it a nine out of ten. 

We mainly used the solution with Jira software in a DevOps context or for agile project planning and management for our developers. We use our Jira Server to manage our IT and DevOps teams and Confluence for general company-wide purposes as an internal knowledge repository. Bitbucket is used for standard purposes.

Bitbucket Server integrates well with other products.

The user experience is tedious and long-winded. It could also be smoother from an admin's perspective. Finding settings or working with it is also a bit slow and not very intuitive.

The main limitation of Bitbucket Server is the lack of certain features. Many basic features are missing and must be supplemented through the Atlassian marketplace. Additionally, Bitbucket Server lacks support from third-party applications and tools.

I have been using Bitbucket Server as a partner for two years.

I rate the solution’s stability a seven out of ten.

The solution is scalable. The challenges in user intuitiveness when working with Bitbucket Server and R. The less smooth the processes, the harder the tool is to work with, and the more difficult it becomes to scale. Additionally, Atlassian products are known to experience downtime occasionally and lack adequate support, which affects their stability and reliability.

I rate the solution’s scalability a seven out of ten.

The initial setup is straightforward and takes less than a day to complete. Two people are required for it.

The pricing is competitive. A few basic tiers are priced at a few dollars, like three dollars per user per month.

Either use Bitbucket alongside the rest of the Atlassian suite or invest significantly more admin time into syncing it than with other products.

Overall, I rate the solution a seven out of ten.

I use the solution in my company to store source code and for version control.

The solution's most valuable features are its ease of use and huge integration features with multiple tools like Jenkins and Jira. My company also gets a build status notification from Jenkins to Bitbucket.

I don't see any complexity involved in the product, especially since some of its users are DevOps engineers. My company works less in the area of storing source codes using the product. My company mainly works in the integration area, after which we design and provide the guidelines for new branching strategies.

The response time of the product's support team may not be good enough to meet the expectations of users, making it an area where improvements are required.

It would be nice if users had the option to download a build directly from Bitbucket in the future.

I have been using Bitbucket Server for six years. I am just a customer of Atlassian.

I have not experienced any glitches while using the product.

There is a different team maintaining Bitbucket Server that also deals with its scalability features.

The solution's technical support is good. I rate the technical support an eight out of ten.

Positive

The product's deployment part is good. My company does not directly deploy the product; instead, we usually store source code using the product. Once the Jenkins build job is completed, we store the binaries in a binary artifact repository, which is where we pick a package when dealing with the deployment phase of Bitbucket Server.

There is a team of administrators who look after the product's deployment process. My company is just a stakeholder, and we administer the user access and the integration areas.

The features I found to be the most valuable in the product for code collaboration stem from the fact that the tool provides webhooks, which are very beneficial for triggering jobs in Jenkins when dealing with new commits, Git push, and Git merge.

Speaking about how the tool's pull request functionality impacted my company's code review process, I would say that when a pull request is created, it goes to the technical team leader and PO. After my company gets comments from the tech lead or PO, the pull request will be merged with the targeted branch.

The integration capabilities of the product are good since it can integrate with multiple products.

The product is easy to maintain.

I recommend the product to others who plan to use it.

I rate the tool a ten out of ten.

We use Bitbucket to install software tools by storing the code and configuring the development.

I believe it's user-friendly for our developers, and it's effective in terms of traceability for tracking our actions.

I don't have many complaints from the developers' project.

I have been using Bitbucket Server for the last 10 years. 

It is stable and rate it a nine out of ten. 

I find it reasonably scalable.

I have no complaints about Atlassian's tech support, and I think it's good.

Positive

We chose it because of its strong community and user-friendliness, but we wanted a hosted solution for better service.

It is quite easy to install. We ensure that Bitbucket is installed on the same day, but it typically takes a day or two for the installation and configuration to be completed.

It’s quite easy to maintain, but we need to set up our monitoring services properly.

We opted for the on-premises solution, and while it's quite expensive, I believe there's room for improvement in terms of pricing. The licensing is based on the number of users, but I'm not entirely certain about the details.

I believe it's a valuable tool for developers to quickly set up and use packages. I would rate it nine out of ten.

When working on code development or maintenance, the initial step involves pushing the code to a central server, to manage code changes and additions. Bitbucket Server is commonly used for pushing and pulling code and plays a pivotal role in this process.

Its standout features are the seamless integration with various intelligent tools and its user-friendly nature.

There are instances when I interact with Bitbucket and encounter a situation where I've pushed changes to the website server. However, when I access my branch on the website server, I notice that the changes are not immediately reflected. Enhancing the real-time reflection of changes online is an area that could benefit from improvement.

I have been working with it for one year.

It offers good stability capabilities.

It demonstrates high scalability, which is essential for my company's substantial workforce, consisting of approximately eight to nine thousand employees. Within my team, we rely on it as our version control system, and nearly two hundred team members actively use it.

In the rare event that we faced downtime, the admin and other teams promptly addressed and resolved the issue.

Neutral

Before we switched to Bitbucket, the company was working with GitHub on the server. Bitbucket is known for its user-friendliness, and personally, I find it very easy to work with.

The initial setup is quite easy.

I would recommend it as it serves as an excellent platform for code maintenance. I would rate it eight out of ten.

Bitbucket Server is a code repository for code pipelines and migration workloads. It helps developers to stage the repository. 

It is a robust tool that offers organizational security. Bitbucket Server's ease of use is a comfort for developers. It has a GitHub backend. Developers can merge their code changes and put them together. 

The most valuable feature of the Bitbucket Server is its ease of management. The solution is easy to manage once we migrate and set up the data.  The solution offers a fast code push feature. 

The product requires patching and version improvements. Some functions do not work properly when we move from one version to another. We need a technical improvement.  Also, communicating with other Atlassian products becomes cumbersome when we move from one version to another. I want Bitbucket Server to include a dashboard similar to Jira's. Atlassian must also develop a tool to scan our complete base for vulnerabilities. 

I have been working with the product since 2016. 

The product's stability is good. 

The tool's scalability is good; I rate it a ten out of ten. 

Bitbucket Server's setup was straightforward. However, data migration was complex because we moved from on-premises database to PostgreSQL to RDS. 

We have seen ROI with Bitbucket Server's use. 

The solution comes as a part of the whole suite. 

The tool's scalability and security are good. It can be integrated with multiple devices. I rate it a ten out of ten.