I have used Google Cloud Platform and Amazon AWS for implementing Bamboo. It is not difficult to complete.

The length of time it takes for deployment depends on a lot of variables, such as how the pipeline is deployed and what type of infrastructure is present. However, it typically takes only hours not days. 

I rate the setup of Bamboo a nine out of ten.

The initial setup is easy. I rate the process an eight out of ten.

The complexity of implementing Bamboo varies based on the client's specific needs. Installing and obtaining basic information is simple, but building a pipeline can be more challenging. This task is typically handled by a DevOps engineer.

Unless requested by the client, the implementation would not be handled by the partner, which can be quite challenging. 

The installation and configuration can be straightforward. 

Excluding the pipeline, the full implementation can be done in two days.

Typically, the implementation process involves setting up the infrastructure and ensuring that all prerequisites are met, including the necessary platforms and versions compatible with Bamboo. The deployment complexity varies depending on whether it's done on Linux or Microsoft Windows OS. The deployment process on Microsoft Windows OS is relatively straightforward, requiring the installation of prerequisites and a supported DB server. If deployed on a PC, a shared network folder with the appropriate security access is also necessary. These steps are well-documented, making them easy to follow. Therefore, deployment is not overly challenging. However, configuring the system from within can be more complicated.

I rate the initial setup from Bamboo a seven out of ten.

The product's initial setup phase is okay for us since our company is an expert in it.

The solution is deployed on the cloud.

The initial setup was straightforward but we are an IT company so did this easily with the resources we have. 

The initial setup was a lovely experience for us because the first time we tried it, it was ok.

If we compare the initial setup of Bamboo's with Jenkins, Jenkins's setup is easier. Bamboo comes with more configuration when you start setting it up. However, Bamboo is more of an enterprise tool as compared to Jenkins because it supports different databases. You can configure Bamboo with MySQL, Oracle, or any database. This is why the setup, requires more configuration, but the setup is straightforward. It is not that complex, once a person has done it they become aware of it and can do it again with less trouble.

Its initial setup is complex.

It was pretty straightforward. Atlassian standardizes setup across products for the most part, so it was easy for us to install, configure, and navigate.

They need to work on their upgrade paths and deployments. If you fall to a few versions behind you may end up doing a multi-version installation. Not fun.

Bamboo is very easy to deploy, all it takes is extracting the distribution and a JRE to run it. This also goes for the remote agents which install by running a JAR which already contains the configuration for communicating with its master.

It was straightforward, although, Bamboo initially creates its main install folder in the home directory of the current user. Even though Bamboo has a 'bamboo.home', Bamboo organizes its different library/build-time/resource component folders separately in the configuration and modifying those proved intensive in comparison to TeamCity and Jenkins where there's is only one 'Home' folder.

It was straightforward, as the default agent and remote agents install out-of-the-box. Only some memory tuning was needed.

Easy. Just like other Atlassian products.

I wasn't really involved in the implementation process so I can't really comment on it. 

We have two administrators on the solution currently.