Bitbucket Server Reviews

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.

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.

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. 

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. 

The product’s most valuable features are private repositories and the ability to work as a proxy for implementing CI/CD pipelines.

The product interface consists of multiple features that are complicated to navigate for new users. They could make it easier to access and introduce templates with sample code for beginners to understand Kubernetes deployment.

We have been using Bitbucket Server for eight years.

It is a perfectly stable platform.

We have 37,000 Bitbucket Server users in our organization. We plan to increase the usage.

We use Jira and Confluence.

The initial setup is simple for me as I am an experienced developer. For our private cloud setup, the process was streamlined, given the enterprise-level support and production coverage.

Bitbucket significantly improves our code review and collaboration processes by providing private repositories as a default feature. This specific feature was not available in GitHub at the time of our selection. 

We utilize a standard Gitflow with feature branches, including branches like bugfixes, hotfixes, and more. It makes the request mechanism easy to use.

Its integration capabilities with other tools have been useful. However, the integration with Slack needs improvement. It provides satisfactory performance and scalability for our site.

I recommend it to others and rate it a nine out of ten.

I lead a testing team for a company, and all my QAs use Bitbucket Server to store their automation testing code.

Bitbucket Server easily integrates with Jira because they are both Atlassian products. The solution's integration with Jenkins is also easy.

The solution's user interface could be improved because it's not very user-friendly or intuitive. It feels like old HTML blocks were used to build the user interface.

Some supporting documentation for Bitbucket Server would be helpful because it's not very easy to get information about it. I remember having to Google a few times to figure out how to do something on Bitbucket Server.

I have been using Bitbucket Server for two years.

I haven’t faced any issues with the solution’s stability.

I rate Bitbucket Server ten out of ten for stability.

We've been only using the solution as a repository, and we haven't faced any challenges with its scalability.

I rate Bitbucket Server a six out of ten for scalability.

The solution's technical support is not good. They pick keywords from the customer's email and send some automated standard responses that have been copypasted, which doesn't help.

Negative

Bitbucket Server is quite expensive compared to other products. We pay a monthly licensing fee for the solution.

I am open to exploring other products because while Bitbucket Server does the job, there are better tools in the market that I need to explore.

Overall, I rate Bitbucket Server a five out of ten.

I use Bitbucket Server to store code. 

The tool makes pushing codes and setting up CI/CD pipelines easy. 

Bitbucket Server has limited user support for its free version. It is expensive. 

I have been using the product for two years. 

I rate the tool's stability a nine out of ten. 

Bitbucket Server is scalable. 

I have worked with GitHub and GitLab. 

The tool's deployment is straightforward. 

Bitbucket Server's deployment can be done in-house. 

Bitbucket Server saves a lot of money. 

I rate Bitbucket Server a 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.

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.

Bitbucket Server I use for a software repository that has code inside.

Bitbucket Server is easy to use. You can use other applications to access it, or you can use it to access the internet. You can use solutions, such as Sourcetree, which is free, and put it on your development system and use it to do the check-in, checkouts, and those type of operations. It is nice, but some other developers may agree.

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

Bitbucket Server is stable.

Bitbucket Server is scalable because the developers are putting things in it they're not supposed to, such as binary data, and it's more or less a text code repository.

We have approximately 150 user licenses. Sometimes vendors will have licenses in chunks. For example, from 50 to 150 or 200. There's no in-between, sometimes you have to buy more licenses than you need.

I have not needed to use technical support. I am good with using this solution and can figure out problems myself or I can use the internet and find a solution.

The initial setup is straightforward.

I can do the integration and setup of the solution. There requires one person to do the maintenance of the solution. The solution is low maintenance. If a patch comes out, and it affects you then you need to do something. If it does not, then you do not need to do anything.

There is a cost to use this solution but it is based on how many users are using it. If you have 50 users or 1,000 users the price will be very different.

Bitbucket Server can be expensive and they want you to purchase their cloud solution. They are getting rid of their on-premises solution, however, you can still find them.

Atlassian tools seem to use Log4j quite a bit, and they should get away from it because of the recent security issues that have happened in the last few days.

I rate Bitbucket Server a six out of ten.