Likelihood to Recommend Maven is great if you have an application with a lot of third-party dependencies and don’t want each developer to keep track of where the dependency can be downloaded. It’s also a great way to make it easy for a new developer to be able to build the application. It’s less suitable for simple projects without any third-party dependencies.
Read full review The thing I mentioned earlier where we're constantly dealing with federal regulations or new agents that they want us to install and deploy and just getting those out in a consistent manner in a canned installation via Playbook is ideal
Read full review Pros If you are building in the Java ecosystem, then Maven definitely has the biggest repository of artifacts needed for such projects. It has a very simple to use extendable architecture. Everything is configurable through the Pom.xml file which is very simple to follow. Read full review Makes it easy to create and share automation in one central hub. Ansible content collections give me the ability to reuse code, making it rapid to carry out complex IT processes. Event-driven automation allows me to reduce manual tasks: it is rapid to know which action to take and respond automatically by receiving events from external apps automatically. Read full review Cons Maven provides a very rigid model that makes customization tedious and sometimes impossible. While this can make it easier to understand any given Maven build, as long as you don’t have any special requirements, it also makes it unsuitable for many automation problems. Maven has few, built-in dependency scopes, which forces awkward module architectures in common scenarios like using test fixtures or code generation. There is no separation between unit and integration tests Read full review Workflows should have more flexible paths than just success or failure. The upgrade process can be challenging with differences in security and environment. There is an opportunity to add CICD functionality into the tool. For development, it would be nice to have the option of editing a repo directly from AAP to allow quick tests/reruns. Then, allow it to push the updates back or create a new branch/PR in GitHub. The RBAC is good but could use improvements. One example would be an option that allows admins to assume the access of another user to validate it works as expected. Read full review Likelihood to Renew We are deploying Ansible at all levels of the organization
Read full review Usability The overall usability of Apache Maven is very good to us. We were able to incorporate it into our company's build process pretty quickly. We deployed it to multiple teams throughout the entire enterprise. We got good feedback from our developers stating that Apache Maven has simplified their build process. It also allowed to to standardize the build process for the entire enterprise, thus ensure that each development team is using the same, consistent process to build code.
Read full review 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 I can't speak to the support, as I've never had issues. Apache Maven "just works," and errors were user errors or local nexus errors. Apache Maven is a great build/dependency management tool. I give it a 9/10 because occasionally the error message don't immediately indicate a solution...but again, those errors were always user or configuration errors, and the Maven documentation is extensive, so I don't find fault in Maven, but in its users.
Read full review 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 Ant, Maven's opposing framework, is often a point of comparison. Although Ant does not require formal conventions, it is procedural in the sense that you must tell Ant exactly what to do and when. It also lacks a lifecycle, along with goal definition and dependencies. Maven, on the other hand, requires less work as it knows exactly where your source code is as long as the pom.xml file is generated.
Read full review AAP doesn't truly stack up against any of the products mentioned except for
Aria Automation. But, it is extensible and open and has a lower cost to entry.
Read full review Return on Investment Apache Maven is an open source product from the Apache Software Foundation. Being free to use without any licensing constraints, we've been very happy with this product thus far. The software build and packaging times for our applications have improved greatly since our use of this tool. 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