I'm mainly using Bitbucket as a code repository for storing the configurations and templates of my monitoring tools. We have them stored locally, and Bitbucket manages changes and builds, so we have a means of rolling back if there are any issues. 

There are about 10 to 15 users in the company at the moment. They want to expand usage, but there's still little uptake. It's an old-fashioned, traditional IT  place that they work in.

We mainly use Bitbucket as a code repository. The solution provides a nice user interface where we can track every change. Bitbucket uses Git as a binary in the backend, so it's pretty simple for developers and administrators to take care of every commit. Moreover, Bitbucket is easy to integrate with Atlassian tools, like the Jira-to-Bitbucket plugin. We also use the Jira-to-Jenkins plugin and Bitbucket-to-Jenkins plugin. As part of the work solution, when we used Jenkins as CI, it also integrated with Bitbucket and Jira. Any changes are compiled and pushed into the Artifactory or another artifact-containing tool. Each commit that Jenkins compiles has automatically been reflected in Bitbucket. You can take a reference opposite to each commit, like "this is being compiled" and "this belongs to a particular Jira ticket." It's pretty simple to track each change.

I use it to monitor developers' progress and occasionally check in on ongoing activities to stay informed about the project's status.

I use the solution for my company's customers, for whom I take care of the version controlling of source codes.

I use Bitbucket for plugins and Active Directory integration. It helps me onboard users for an automation suit. I also use it to check codes and generate reports on a daily basis. 

We have around 700 users for this product in our company and a maintenance team of four people. I've recently put in an order to increase that to 1,000 users in the near future and hope to bump this up to 2,000 users down the track. We are end users of this solution and I'm the Head of the DevOps Engineering Center.

We use Bitbucket for managing and merging code versions, as well as for continuous integration when deploying code to different environments. It helps us to identify and resolve conflicts and to track the changes made to the code by different developers.

Our primary use case is version control, integration with Jenkins for build management, and integration to Jira so that there is traceability to any issues from the build. We also work with code review and pull requests.

We use Bitbucket to store all of our code repositories. It has become the standardized tool for code management across all teams.

I use the solution mainly to control and share code within the team. I also use it to secure my parts and deploy my code. Overall, Bitbucket is for DevOps purposes.

We work on two or three different solutions, and we have some IoT devices that we collect some data from. That is a separate solution we use to identify customer flow and is on-premises. Though there is hardware for the basic part of the solution, we have cloud-based applications that collect data directly from that application.

Besides that, our primary ERP machine, an ERP server, dynamically provides financial operations. It contains everything about us and is cloud-based. Our third team is Power BI, and though it is cloud-based, the core is our data.

We collect data from all three sources for analysis and have a big setup for data computation, integration, and analysis. We use a database on-premises for that. We also use some Azure services, but not as much because we mainly use our database on-premises, and we integrate our cloud solutions directly with that. We have very high-speed Internet, so our customer and employee loyalty and mobile applications are different applications we use, all integrated with that specific database, and it is very smooth. Our primary applications are hosted on the cloud, and our analytical part is hosted on our private cloud.

Actually, I have an E-commerce product on that solution and store it there. I deploy the product for each customer and they use it. I'm trying to use the cloud system as my center for distribution. I use Bitbucket for hosting the core code.

We use Bitbucket for code management.

Bitbucket is the factor standard for development nowadays.

We use Bitbucket as a repository for our sensitive data, like source code and any other sensitive information that requires change and version tracking. We have eight to 10 users currently accessing Bitbucket.

We use the solution for source control.

The solution is used for web-development

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

We use Bitbucket as our code repository and base it on our DevOps process.

My company uses Bitbucket for version control and codes that we use for transforming data.

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

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

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

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

We use Bitbucket in our company for source code management.

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

Our company uses the solution for code management. 

Our primary use case is for an ICM tool. Just source code. 

We are using Bitbucket for the code checking and tracking of our project depositories which we have locally. This includes code changes in software development. 

We use Bitbucket to store the company's proprietary code and open-source projects and share them internally. 

It's a source control system. We have lots of source code and we wanted to move to Git and there are a lot of different Git solutions out there, including free stuff. But we liked the features of Bitbucket, because it takes off some of the sharp edges, so to speak. It's a more professional version than the free open source Git that's widely available.

Bitbucket, like GitHub, serves as a repository for coding and facilitates integration management and version control. It has features related to these aspects.

We use BitBucket as a repository for backing up our VS code. 

Bitbucket is our source code repository. We use it as our source code reaction control system and for pool requests and engineer builds. It is integrated with Bamboo, which uses a CI CD pipeline to release our code to different environments.

Our primary use case of this solution is as source repository. We use it to store all the source codes. So we basically use it for easy management of access to the source repository and creating pull requests. It also helps us to manage and get an overview of the different branches we have. It integrates into JIRA seamlessly so you can see the task effects on a JIRA task and Git.

We develop our own applications and all of our source code activities are managed and tracked on Bitbucket.

We're using Bitbucket for version control and deployment.

Our primary use case is for source coding and continuous integration.

Bitbucket has a global way of collecting data from air conditioners and real-time data collection for global customers.

We primarily use the solution for managing our own repository.