Bitbucket Server Reviews

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.

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. 

Bitbucket Server serves as our source code management and version control platform. Like Azure Repository, we utilize it to store and manage our source code. The integration of Bitbucket into our Software Development Life Cycle process is crucial. However, it's important to note that the product does not provide code approval functionalities. We may need to employ additional tools, such as Jenkins, for code approvals. Additional tools from Jira and Jenkins help in the CI/CD process. 

As part of our SDLC life cycle, Bitbucket provides us source code management, versioning, branching etc.

we can link source code to our SDLC changes and release the source code as part of release process.

Bitbucket Server supports code collaboration by providing commands developers can use to check in code. Through comments, developers can specify the purpose of the code check-in. Additionally, Bitbucket allows tagging of code for releases.

Bitbucket Server can experience performance issues when pushing a large amount of code. This process may take a considerable amount of time.

We are using bitbucket for almost 6 years, it is integrated with Jira, currently we are only using it as source code repository. not as CI/CD platform.

The product is generally stable, with occasional hiccups or errors that might occur.

The solution can be scaled vertically or horizontally as per the requirement. My company has eight to ten users. 

The tool's support is standard. They respond as soon as possible. 

The tool's deployment requires expertise since its environment is on-premise. To deploy Bitbucket Server, you must run the standalone executable file and set up the database server since it stores metadata in the database. Additionally, you'll require a shared folder to keep the actual code. Configuration of URLs and a server proxy are necessary for the deployment process. There are one to two engineers who manage the tool. 

The solution's deployment requires a consultant. 

The tool's licensing costs are yearly. Prices can become expensive if you have a lot of users. 

The product is good, but its features are limited. It is a good choice if the requirement is solely to manage source code. It handles source code management, providing stable check-in and check-out functionality and features like comments and tagging. You can set permissions at the project level, repository level, or branch level. Project-level permissions apply to all branches and repositories within the project. Repository-level permissions are specific to the branches within that repository. I rate it a seven out of ten. 

The solution can easily integrate with Jira and other Atlassian products. 

We mainly use Bitbucket Server for CI/CD. We had around two to three members working on the same project for automation. To manage version control, we used Bitbucket to collaborate and integrate with other resources. 

We created separate repositories for each endpoint, including API endpoints and different applications. We also set up separate pipelines for each of them. The customer had a specific requirement, so we created the necessary repositories and hosted the configuration server.

Earlier, we configured triggers and hooks on the Bitbucket Server. This setup allowed automated triggering whenever someone pushed code to a branch. Depending on the trigger, the pipeline would run on BuildKite or another CI/CD tool.

The most valuable feature is that it has its own pipelines.

The UI could be enhanced.

I have been using Bitbucket Server for around two and a half years.

We never had any downtime, performance issues with the Bitbucket Server.

10-12 members are using the Bitbucket Server.

Initially, we started using Bitbucket Server about a year ago, primarily for managing our build processes with the build guide. Since then, we have increasingly adopted Python. Initially, we had only two repositories, but now we have expanded to twelve to thirteen repositories.

Bitbucket has a lot of features compared to GitHub.

The initial setup is straightforward.

If you're going to use a version control system, Bitbucket Server is a good choice.

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

The use case for Bitbucket is a good repository manager for the code base. It is one type of version control system on the cloud.

The platform's most beneficial feature is the repository for our code base. It helps with versioning, Git collaboration, merging, and cloning. It can efficiently promote code to different environments, like development to UAT and production.

The platform's integration with other cloud services should be improved.

I have been using Bitbucket Server for four years. 

The product stability is excellent on the cloud. I rate the stability on-premises at about nine out of ten.

The technical support services are good. 

The product doesn't require any setup when deployed on the cloud. Whereas, we have to follow a deployment process for the on-premises version. 

Pull request features are essential for verifying repositories on the cloud and should be pulled to the local workstation. Pull requests (PR) help merge branches and are part of Git collaboration tools like Bitbucket and GitHub.

The current trend in our industry is towards highly integrated systems. Most companies are choosing their software development lifecycle tools based on integration capabilities. So, integration is a key focus right now.

I rate Bitbucket Server nine out of ten. 

It would have been better to use Bitbucket Server if it had something similar to the concept called GitHub Actions since it allows GitHub to provide seamless integration of CI/CD pipelines.

I have experience with Bitbucket Server. I am a customer of the product.

It is a stable solution

It is an easily scalable solution.

I don't have experience with the solution's technical support. I rate the technical support a seven to eight out of ten.

Neutral

I have experience with GitHub and GitLab. Compared to GitHub and GitLab, Bitbucket Server provides better security levels of verification. Bitbucket Server's pricing options are cheaper than GitHub and GitLab. In general, GitHub is much better than Bitbucket Server. Bitbucket Server's prices are cheaper than GitHub.

The product's initial setup phase was neither a difficult nor easy process, making it a moderate process. GitHub is much easier from a deployment perspective, especially from the CI/CD angle for continuous integrations and deployments. Security-wise, Bitbucket Server offers some additional steps allowing you to use a secured authentication process, like single sign-on, authenticated sign-on, or additional two-factor verification, which is better in Bitbucket Server compared to GitHub.

Bitbucket Server enhances collaboration in our company's development workflow since its users are developers who use CodeCommit. Areas like release planning and code movement from development to integration to testing and from production to deployment are managed with Bitbucket Server. Most of the code repositories are also on Bitbucket Server.

The features of Bitbucket Server that I found most beneficial for source code management stem from its integration capabilities with code repositories that are supposed to be from different branches. Basically, integration is easier in Bitbucket Server. Deployment is also pretty seamless across from Bitbucket Server's side. Fetching the code from the repo branch and deploying it is easy.

Bitbucket Server's pull request feature impacted our company's code review process since any kind of difference in the code could be analyzed more easily. The branches could be analyzed better, while the CI/CD integration is also pretty easy with Bitbucket Server. The tool shows you the whole branch of how the code is being used. The data lineage is pretty seamless.

There is a separate team in my company that takes care of the maintenance part of the product.

The integration of Bitbucket Server with other Atlassian products improves our company's project management since we get to know the status once we commit the code as the CodeCommit status is usually reflected in Jira, and it is easily observable allowing users to see what changes have happened. Users can get a unified view of each task or each project, along with details on what code is associated with which step and how Jira commits across. The tool provides a single unified view for code management and project planning.

Bitbucket Server's permission management helped maintain the security of our company's code base, as it is an area that has to do more with the authentication and authorization levels.

I rate the tool a seven out of ten.

In my company, we use Bitbucket Server for managing the repositories since we tend to have different repositories for a particular project, like a back-end, front-end, and the UI, while sometimes everything remains the same.

An organization has to have a repository either way, and it is better to go with Bitbucket Server since it is one of the main tools everybody uses in the market to manage their repositories.

The solution's most valuable feature is that it is simpler in terms of code changes since you just have to map it to a sourcetree and commit changes, after which the user can go for check-in and check-out. Bitbucket Server's version control is amazing.

We had issues in terms of logs, URLs, and cloning the repositories, which is the same issue we keep facing in our company though we manage to resolve it each time. The aforementioned problems make the solution a bit tricky, so it would be great if Bitbucket could provide users with a smoother approach or process when they face an issue. At the moment, there are not many details on how to proceed with the troubleshooting if one of the users faces an issue with the product.

I have been using Bitbucket Server for four years. I use the solution's latest version.

It is an amazingly stable solution.

I won't be able to comment on the product's scalability since it is a repository used in our company. I am unsure of how to scale up Bitbucket Server in my company, and I know that the repository has nothing to do with this storage space in the product. Our company has not encountered use cases where we need to scale up the repository.

The architect developers, consisting of around eight to nine members in our company, use the solution since they have access to it.

In our company, we contacted the technical support team when there was a need to know the endpoints, where you have to configure it properly and authenticate it. We had faced some cloning and access issues, and as of now, these issues have been sorted out.

Bitbucket Server's technical support team was good. In our company, we also have different technical support teams specifically dedicated to each of the products we use.

The initial setup of the tool was very easy.

The solution is deployed on the cloud.

My team does not manage the maintenance and deployments of the solution. For maintenance and deployments, we speak with Jira team. For each of the products that we use in our organization, we have a separate team to manage a particular product. There is a separate team to manage products that fall under Microsoft Office, while another team manages AWS products used in our company. We have to reach out to Jira and raise a ticket to let them know the products we need from their catalog before coming up with the list of what we want and submitting it to Jira, which then provides the licenses for each user.

My suggestion to those planning to buy the solution is to use the product to its full extent since it is a strong and stable product.

I rate the overall product an eight out of ten.