Once we were able to understand how to create the processes and model the manual deployments into automated deployments everything was incremental. We have almost 200 different automation flows and processes(per environment) running in a multi environment ecosystem(dev,qa,pet,prod,dr). Integrated with git, UrbanCode Build and/or other Jenkins pipelines which co-exist in a large organization. As any tool there is resistance from the developers and support people to use it at the beginning, but once they get familiar with the tool they really see the benefit of them being in control of the automated deployment and reducing the workload for them.

availability for the plugins needed in our company, security and auditing of all the operations executed. easy implementation of the agent. Reliability for the application in a complex multi-tiered environment with hundreds of applications.

Cost per agent can be a deterrent to purchase the application but in an enterprise environment. There are ways to reduce that by creating security keys to deploy the processes with a limited number of agents in a secure way.

We were compelled and used rather than satisfied overall.

It took some time to understand its usage and it is complicated.

The price is expensive and it is unreasonable to buy it alone. If it is bought on behalf of the institution and in bulk, it will be somewhat comfortable.