Likelihood to Recommend
If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as Jenkins, if you don't [mind] putting in a little extra elbow grease.
Engineer in Research & DevelopmentPharmaceuticals Company, 5001-10,000 employees
That is a big task for all the functionality now in Ansible Collections - Ethernet Networking, Fibre Channel Networking, Wireless networking, LB/ADC configuration & changes. Storage config and changes, VMware provisioning and changes, Windows Desktop provision when paired w/ a tool like Zuul, Workflow integration w/ ServiceNow (SNOW), Testing framework such as Molecule really all you to ensure what you have in your playbooks is solid...prior to deployment not when released to your consumers; Critical. Consistent runbooks instead of managing tons of scripts allows for cross-team training and functionality in a true disaster scenario. Additionally, conversion tools from other IT automation offerings Puppet and Chef, integration into Cloud environments. The list grows daily so jump in the water is just right!
Engineer in EngineeringInformation Technology and Services Company, 501-1000 employees
- 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.
- 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.
- 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
- 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.
Based on 2 answers
Bamboo was fairly easy to navigate but in the end it always felt as if it was developed as a bolt-on and not a true group up user interface. There were multiple ways to get to everything and the path was never the same. So it was difficult for users to really get a feel of how to use the application.
Based on 1 answer
I would say that a baseline of understanding about how to work with Kubernetes/OpenShift and YAML files is a prerequisite to using Red Hat Ansible Automation Platform. Once those baselines are established, being able to use this platform is much simpler. Red Hat has done a great job in documentation and making Red Hat Ansible Automation Platform something useful for DevOps to quickly get pipelines and configurations up and running quickly.
Engineer in Research & DevelopmentEducation Management Company, 1001-5000 employees
No answers yet
No answers on this topic
Based on 10 answers
Ansible is very friendly to start with. With just a few configurations, you have full management to your servers. You can configure it and implement it in seconds. You can also set up a cron job to make sure it gets implemented. It suits our need perfectly. Support can be a bit hard.
Engineer in Information TechnologyInsurance Company, 10,001+ employees
Based on 14 answers
C-Level Executive in EngineeringInformation Technology & Services Company, 1-10 employees
Based on 5 answers
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
Employee in Information TechnologyComputer Software Company, 1-10 employees
Ansible is a great product, which we really love as it is compatible running along side and with other DevOps tool. The integration features allows other teams to participate in our shared objective. Ansible is easy to use as many programmers are familiar with Python and RHEL. We selected Ansible because its easy barrier to entry and pricing model for new users with not many nodes to manage. We will continue to develop and on-board teams and monitor the scaling abilities of Ansible.
Engineer in Information TechnologyHospital & Health Care Company, 10,001+ employees
Return on Investment
- 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.
- 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.
Premium Consulting/Integration Services—
Entry-level set up fee?
Bamboo Editions & Modules
Additional Pricing Details—
Premium Consulting/Integration Services—
Entry-level set up fee?
Ansible Editions & Modules
- per year