What users are saying about
98 Ratings
3 Ratings
98 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.5 out of 101
3 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.2 out of 101

Likelihood to Recommend

Ansible

Great for automating groups of servers and ensuring updates are pushed to all of them (simultaneously if needed). It's hard to manage large groups of servers, and this tool makes it almost too simple. If there is only one server that is unique from the others, Ansible will not be as useful, but can still help track your changes.
Dylan Cauwels profile photo

XL Release

XL release fits very well when you need cross-team coordination in a release process where you want to coordinate an alpha or beta program with marketing as part of a major release process.
Kenneth Dick profile photo

Pros

Ansible

  • 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.
John Grosjean profile photo

XL Release

  • Cross-team release workflow control using email, texts, scripts allow our release management to be truly a 360 process.
  • XL Release allowing our Jenkins toolchain to control the beginning of release trains which is very powerful.
  • XL release allows us to expose the business process flow for anyone to read direct at the source which runs the process instead of a separate vision.
Kenneth Dick profile photo

Cons

Ansible

  • Unlike Chef, Ansible employes a Push methodology rather than Pull. We found that this doesn't scale well for us, thus we had to consider using Ansible Tower in order to scale.
  • Ansible's free training and tutorials do no provide as much depth and ease for first time users trying it out for the first time.
  • From the limited experience we have had with Ansible Tower, the UI is not very user friendly. There's a lot of bells and whistles that can prove o be overwhelming at times.
No photo available

XL Release

  • XL release is really only missing a consolidated calendar view where you can see the planned activity for the next month, it only knows about what is in progress.
Kenneth Dick profile photo

Performance

Ansible

Ansible 8.4
Based on 5 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.
No photo available

XL Release

No score
No answers yet
No answers on this topic

Alternatives Considered

Ansible

Ansible is sufficient for our purposes because our configurations are relatively simple. Chef and Puppet would work better for more complex configurations. Also, our applications are deployed using Docker which simplifies our configuration requirements. An organization with more complex configurations would find Chef or Puppet suits their needs better.
Chien Huey profile photo

XL Release

XL release is simpler to configure and deploy to the organization than other change management platforms I have used. That simplicity has minor drawbacks requiring you to fit into a limited set of control methods but that exercise helped us simplify a needlessly onerous process.
Kenneth Dick profile photo

Return on Investment

Ansible

  • 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.
James McCoy profile photo

XL Release

  • XL release has improved our consistency of release process, removing multiple days worth of manual status checking and coordination.
  • XL release has allowed us to increase the number of beta releases we can support due to simplifying our release actions.
Kenneth Dick profile photo

Pricing Details

Ansible

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

XL Release

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison