Likelihood to Recommend Previously, our team used
Jenkins . However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
Read full review It has helped save us so much time, as it was designed to automate mundane and repetitive tasks that we were using other tools to perform and that required so much manual intervention. It does not work very well within Windows environments, understandably, but I would love to see more integration. I want it to be sexy and attractive to more than just geeky sysadmins.
Read full review Pros Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM. The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones. Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems. Read full review Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks. Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do. Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to. Read full review Cons UI can be improved Location for settings can be re-arranged API for setting up pipeline Read full review YAML is hard for many to adopt. Moving to a system that is not as white space sensitive would likely increase uptake. AAP and EDA should be more closely aligned. There are differences that can trip users of the integration up. An example would be the way that variables are used. Event-driven Ansible output is not as informative as AAP. Read full review Likelihood to Renew We are deploying Ansible at all levels of the organization
Read full review Usability the yaml is easy to write and most people can be taught to write basic playbooks in a few weeks
Read full review Performance Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
Read full review Support Rating 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.
Read full review Implementation Rating I spoke on this topic today!
Read full review Alternatives Considered GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Read full review I haven't thought of any right now other than just doing our own home-brewed shell scripts. Command line scripts. And how does this compare? It's light years ahead, especially with the ability to share credentials without giving the person the actual credentials. You can delegate that within, I guess what used to be called Ansible Tower, which is now the Ansible Automation platform. It lets you share, I can give you the keys without you being able to see the keys. It's great
Read full review Return on Investment ROI has been good since it's open source Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date Read full review Red Hat Ansible Automation Platform offers automation and ML tools that allow me to automate complex IT tasks. Through automation analytics, it is seamless to gain full visibility into automation performance allowing me to make informed decisions. Red Hat Ansible Automation Platform allows me to move rapidly from insights to action. Creating and sharing automation content in one place unify a team in one place hence enhancing real-time collaboration. Read full review ScreenShots