Bamboo vs Ansible

• Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.
• Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.
• Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.

Read full review

• Agentless. For our implementation, this is the single biggest factor. If we have to touch the machine and install an agent before we can start managing it, that's already too much effort and slows us down.
• Re-entrant. This is not unique to Ansible, but certainly a huge improvement over custom scripts and such. Because it's such a huge effort to make scripts re-entrant, most of our scripts did not allow an elegant way to recover on failure. Manually cleaning up the half-attempt and re-trying is still too cumbersome, and being able to just re-run Ansible is a great improvement!
• Infrastructure as code. This is new to Ansible, and there are still a few minor bugs with their AWS modules, but it's been a huge help being able to define our infrastructure in an Ansible playbook, commit it to source control, and use one tool for all our DevOps tasks.

Read full review

• Extremely hard barrier to entry for non-backend developers
• Blackbox makes it hard to customize functionality
• The inability to add features without breaking core functionality
• No cloud solution
• Tasks cannot be put in if/else statements
• No clear right way to form build plans

Read full review

• Ansible Tower is a paid service, which can be annoying at times. But that is understandable, as it requires an additional level of support from the Ansible team to develop.
• There is a decently large learning curve for someone not familiar with setting up Unix environments. However, there is a very large support community with tons of documentation, so it's not a dealbreaker.

Read full review

• It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.
• Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.
• Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.

Read full review

• We have been able to deploy solutions to client issues without impacting uptime.
• Most system administration tasks have been automated so I am now free to work on architectural improvements or customer support.
• Our customer support has improved thanks to Ansible as it has allowed me more time away from repetitive system activities so I may assist with customer questions and application testing.

Read full review