Bamboo

The vast majority of our organization uses Bamboo for our CICD pipelines. It handles building our applications, running code quality and security scans, running unit & integration tests, and deploying our applications to multiple environments - usually to Cloud Foundry or virtual machines. We sometimes use it for automated reporting or operations tasks such as restarting applications.

Bamboo is being used by our Organization to continuously deploy to our internal applications and environments. It is mainly used by developers and DevOps engineers, however, some other users have view access to check status of their applications. We have solved a lot of problems, some of them are: automation, agility, integration with other internal applications, tracking, and availability, between others.

Bamboo is used across our organization as a goal and employee review mechanism, as well as for hiring. It streamlines the feedback/review process for employees and is a great centralized location for everything.

Bamboo is used as part of our engineering toolchain to automate our build, release, and deploy processes. Whenever code changes occur, Bamboo will automatically build and test the changes, and our engineers will be notified immediately if something is wrong. When the time comes to deploy changes, Bamboo will automate the whole process from build to make the changing public.

Bamboo is used along with our Atlassian suite of applications and mainly by the development team and client services. Since our company just shifted to continuous integration for updating our public facing products, we have been utilizing this product for code. This process is ongoing and meant as part of our agile product development.

We use Bamboo for our builds due to the capability for deployment pipelines as code. The developers create code to populate their build pipelines, and we push to our deploy tool from there.

We currently use Bamboo to help with our continuous integration and deploy process in our Salesforce workload. We use it to get the latest from Bitbucket and run a compilation before we move the source code up to production. We have used it for testing in the past as well.

We originally used Bamboo as our continuous integration and deployment server that was connected to our Bitbucket repository. We had originally started down this path of making Bitbucket and Bamboo the standard here for code repository and continuous integration and deployment but we had a number of challenges making it work and eventually switched to Azure DevOps. We are now in the process of migrating everything to Azure DevOps.

Our software development department uses Bamboo for Continuous Deployment and Continuous Integration. We use also its integration with Bitbucket and Jira, which allows control and visibility through the entire flow: from the Jira epics/stories/tasks to the revision control version number in Bitbucket to the build number in Bamboo. In all our environments: development, QA, preproduction and production.

Bamboo within our organization is used as a continuous integration and delivery tool, with seamless integration with Atlassian products such as Bitbucket and JIRA. In my team, we use it to manage and build our automated testing scripts which help monitor our highly transactional web application/e-commerce site around the clock, it is an invaluable tool.

Bamboo was brought in as part of the Atlassian toolset to replace our aging build environment in order to help us achieve a continuous integration / continuous delivery build model. Bamboo has helped us modernize our existing build infrastructure by moving from scheduled builds to on-demand builds with each change checked in to source control. Presently, Bamboo is only being used in one division, but we hope to socialize its success to additional divisions.

In my department, Bamboo is used for [the] building process and pipeline. Bamboo has simple build configuration, and seamless integration with JIRA. Bamboo supports builds in any programming language using any build tool, including Ant, Maven, and Make. [There are] lots of popular language integrations with multiple notification methods and great integration with other Atlassian products.

Our software development uses Bamboo for its day to day work, for continuous integration, building and deployment of the code. We are also Atlassian partners, so we very often configure Bamboo for our customers, among the other tools of the Atlassian suite.

I currently support an instance of Bamboo for about 6 BI SQL developers. Prior to implementing Bamboo and database source control, our BI team used the same SQL Server for development, test/QA and production. Anyone in the development world knows this is a recipe for disaster. As part of implementing a controlled and continuously integrated development environment, I needed a tool to build the production server from source control. The most difficult part of this equation was identifying the tool to use to get our database objects into source control, but that is a topic for another day. Turns out the easiest part of implementing the build process was ramping up a Bamboo server that is fully integrated with Bitbucket source control. The best part of the tool is it provides many "out of the box" options to script out your build plan tasks. My previous experience was with Jenkins and Subversion and I had never used Bamboo. It was a quick learning curve to overcome and a very reliable tool once implemented.

Bamboo is being used for automating our build process e.g., achieving continuous integration (CI) in a dev and test environment. This is being used by our specific department and will be used by other departments over the time. Bamboo has helped us to streamline continuous integration, branch merging. And with integration with Active Directory and JIRA we can get an excellent tracking.

It is used for fast and continuous partitioning of build and deployment tasks. Bamboo is a chiefly a continuous integration tool, but it does great in assisting with deployment issues and segregating build tasks to allow you to debug your code. Automated merging of branches is also a great feature.

Bamboo is being used by CDK Global as the primary tool for continuous integration and delivery. We use Bamboo for the build servers at our company, and to deploy to the cloud infrastructure for promotion through various environments like development, development integration, performance, quality assurance, staging, and production.
Bamboo is used across the organization for all R&D of new products. CDK is working to transition all products to use Bamboo, but it has a lot of them. Bamboo solves the problem of needing to build a product in a reproducible way that is not dependant on anything that exists on an individual developer's computer. It allows us to deploy a deterministically generated image from a central location. I think that Bamboo is a good product, but CDK could make better use of it if they could start all over, but they are sort of stuck with the current implementation they have because it is hard to change quickly.

Let me preface this by saying we are "all-in" on the Atlassian suite of products, so integrating Bamboo into our workflow was a no-brainer from the start, since the integration with bitbucket was a snap. It is being used across the entire organization, for both internal and customer-facing apps (mainly due to our tightly integrated tech stack).
The caveat to all of this, is we are currently moving off of Bamboo to TeamCity by Jetbrains, as we were making use of the Bamboo cloud services, and were/are not interested in self-hosting.

As with all Atlassian products, the best part of Bamboo is the integration into their full suite of software. Getting started with Bamboo from a Stash or Bitbucket code repo is as simple as clicking a button, and all downstream changes are immediately tracked and updated. Atlassian has made a huge effort to ensure that the dashboards to monitor build and deployment plans are both useful and informative, and it has paid off in a big way. Users can start, stop, change, monitor, create and delete plans from the push of a single button.

We use Bamboo to continuously build our software whenever anything is checked into our source control system. This lets us stay on top of any problems that could potentially arise from a stray check in. Bamboo does builds for all our various branches and even manages branch merging only if compilation succeeds. It is an indispensable part of our workflow.

Bamboo is an enterprise-friendly continuous deployment and continuous integration tool for hundreds of different application builds to hundreds of different testing environments. We use it within our department of application development. It is used for fast and continuous partitioning of build and deployment tasks. Bamboo is a chiefly a continuous integration tool, but it does great in assisting with deployment issues and segregating build tasks to allow you to debug your code. Automated merging of branches is also a great feature.

It's being used across the organization for our CI/CD server...this includes native Android and iOS apps, mobile and desktop web sites, and the back end. We use Bamboo instead of Jenkins because it's more tightly integrated with other Atlassian tools like JIRA. The server is hosted in-house (Atlassian is discontinuing Bamboo Cloud which I'm not sure was a good idea for them because that just concedes the market to CircleCI, etc.)