Bitbucket Server Reviews

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. 

I use the solution in my company for traditional projects. Now, my company plans to move our projects to GitLab since it provides a single UI for everything.

Bitbucket Server creates a branch and is useful for authentication, commits, and pushing changes.

Bitbucket Server is a standalone tool or server. My company also uses Jira. In our company, there are different kinds of tools linked together by webhooks, and we use Jenkins to run Bitbucket Server. GitLab provides an integrated solution, so everything is available in a single product. With Bitbucket Server, you can see the codes, configure the pipelines, and you can merge a pull request. Bitbucket Server may be even better than GitHub. With GitLab, you have a single solution in one place, so it is not scattered in many places, like in the case of Jira, Jenkins, or Bitbucket Server, making it a better option for our company. From an improvement perspective, Bitbucket Server should make everything available as a single solution.

I have experience with Bitbucket Server.

In our company, Bitbucket Server has a backend link to Jira. When Jira is down, Bitbucket Server is also down.

It is an okay tool in terms of scalability. Though I am unsure, I feel that Oracle DB is used in the backend. In our company, when we have to create new reports in the backend database, you just increase the hard disk. Another team in my company controls the aforementioned area associated with the product, so I don't know it in detail.

Considering that all the developers in my company use the product, I would say that around 30 percent of the people in my company use the solution.

My company decided that since Zscaler is on the cloud, we need a local on-premises server.

The product's initial setup phase is complex. GitLab is better to deal with when it comes to the setup phase since it uses the YAML script. With GitLab, one can use templates for almost all projects, so a given project can be dealt with based on the templates, and sometimes the templates might have to be updated a little bit. In Jenkins, every project is treated separately, so you have to create every project on Jenkinsfile. It cannot be based on some templates, and I feel it may be a little bit complex and not as easy as GitLab.

One needs to pay towards the licensing charges associated with the product.

I am planning to move to GitLab.

In terms of the most valuable feature of the tool for our company's current collaboration, I would say that since the product is deployed on an on-premises model, you can easily control the branching strategy, merge strategies, and code review.

The pull request feature of the tool streamlines the code review process in our company, after which we invite some people to review it and then change the policies if needed. All people involved in the process of reviewing should provide approval based on which the company can delete or merge branches.

For the improvement of CI/CD pipelines, my company uses Jenkins to check the pipelines from the Bitbucket Server. In the pipeline, our company can link to Jira or Confluence and deal with checkout, clone, compile, and then do the test and generate reports.

I recommend the product to others, especially small companies because you can get a cloud solution for your organization, and also, it is similar to GitLab and GitHub. One can work with Bitbucket Server, Jira, and GitLab, along with CI/CD pipelines. Small companies also need not set up on-premises servers and should prefer cloud services.

In terms of benefits, I feel that many companies are moving to Bitbucket Server since it can be deployed on an on-premises model at a time when everything is being moved to the cloud. GitLab can be used by those who want to move to the cloud.

I rate the tool an eight 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. 

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. 

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.

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.