DevOps Engineer at a insurance company with 5,001-10,000 employees
Real User
Top 20
2022-11-07T11:33:01Z
Nov 7, 2022
The interface allows access in a number of ways but that can be confusing. For example, driving to your home from the office is easy when there are one or two routes. With twenty routes, there is some initial confusion.
Software Engineering Director at a transportation company with 10,001+ employees
Real User
2022-01-04T21:39:00Z
Jan 4, 2022
The technical support of the solution could definitely be improved as PMRs take a long to resolve. The cost of the solution is high. It would be good to have the support of public cloud services like Azure. My team has also had some concerns around security when using this solution.
This solution could be made more flexible with respect to deploying databases. Liquibase is a valuable feature but it is weak and could be better. I have just seen a video on a product called Datical, and the database workflows are easy to manage. Not just anybody can use this tool without first taking at least the basic training online. I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline.
Rollout Manager at a transportation company with 1,001-5,000 employees
Real User
2019-03-06T07:41:00Z
Mar 6, 2019
What UrbanCode Deploy improved for us is that we have better visibility. We are not deploying faster with it. Actually, it's a little bit slower. We have the software application automation fully under control with UrbanCode Deploy. Whereas when we did it the old way, we had failures. Before we used UrbanCode Deploy it was difficult to find out why we had failures. Now, we don't have any failures anymore, or almost none. For the last couple of months, we have no failures at all and we have full visibility. The interface is doing very well. Performance-wise, our deployment now takes longer. We know that, but that's something that we can live with to take advantage of UrbanCode Deploy's other feature set. We are one major version behind and we will do the updates internally. The only problem is UrbanCode Deploy is used not only by me but by all of the company. We all do our deployments with UrbanCode. Upgrading is not my decision. I certainly would like to have a better way to pass information between deployment steps using UrbanCode Deploy because that's really difficult to do. Personally, I would like it if you can loop on some things like the tags and the agents. I would like to have some more loops.
IBM UrbanCode Deploy orchestrates and automates the deployment of applications, middleware configuration, and database changes into development, test, and production environments—local, dedicated or shared cloud environments—accelerating time to market and reducing cost by shrinking manual efforts from days to minutes with automation, while reducing risk by cutting deployment errors by up to 90 percent.
The interface allows access in a number of ways but that can be confusing. For example, driving to your home from the office is easy when there are one or two routes. With twenty routes, there is some initial confusion.
The technical support of the solution could definitely be improved as PMRs take a long to resolve. The cost of the solution is high. It would be good to have the support of public cloud services like Azure. My team has also had some concerns around security when using this solution.
I would like to see more reporting for container architecture.
This solution could be made more flexible with respect to deploying databases. Liquibase is a valuable feature but it is weak and could be better. I have just seen a video on a product called Datical, and the database workflows are easy to manage. Not just anybody can use this tool without first taking at least the basic training online. I would like to have the agent up and running at all times, as opposed to only while it is in the DevOps pipeline.
What UrbanCode Deploy improved for us is that we have better visibility. We are not deploying faster with it. Actually, it's a little bit slower. We have the software application automation fully under control with UrbanCode Deploy. Whereas when we did it the old way, we had failures. Before we used UrbanCode Deploy it was difficult to find out why we had failures. Now, we don't have any failures anymore, or almost none. For the last couple of months, we have no failures at all and we have full visibility. The interface is doing very well. Performance-wise, our deployment now takes longer. We know that, but that's something that we can live with to take advantage of UrbanCode Deploy's other feature set. We are one major version behind and we will do the updates internally. The only problem is UrbanCode Deploy is used not only by me but by all of the company. We all do our deployments with UrbanCode. Upgrading is not my decision. I certainly would like to have a better way to pass information between deployment steps using UrbanCode Deploy because that's really difficult to do. Personally, I would like it if you can loop on some things like the tags and the agents. I would like to have some more loops.