Azure Pipelines vs. IBM DevOps Deploy

It is good tool if you are doing continuous improvements in your code and you wish it goes live whenever you push code to GitHub. So integrating Azure Pipeline, it automatically does CI/CD in the background once you push code/merge code and it is live in few minutes. It also does some automated tests if you have wrote scripts

Incentivized

IBM UrbanCode Deploy is excellent for code deployments such as Java, .Net, C++, etc. It can also deploy and run SQLs reasonably well. Where it lacks is the ability for executables, Jars, WARs, EARs, etc.

Incentivized

• Integration with SonarQube
• Integration with Azure DevOps
• Integration with GitHub

Incentivized

• Visual deployment instructions.
• Inventory management of environments.
• Component configuration at a granular level with customization.

Incentivized

• The errors which we got sometimes are not clearly enough.
• There are some let's say hidden options, they could be more visible
• When the process is running we have to remember about manually refreshing to see the current status because it doesn't work automatically

Incentivized

• IBM UrbanCode Deploy does code deployments easy enough, but configurations or ex deployments are a little more complicated. I work on packaged systems, so most of the code I get is form a vendor that I have to deploy.
• IBM UebanCode Deploy integration into the mainframe world would be ideal. My company uses Mainframe and OpenSystems technologies, and many times there are dependencies between the deployments.

Incentivized

It's challenging to get a working knowledge of the product without having someone show you the ropes. Linking components with applications and applications with resource trees and resource trees with application deploys is not intuitive. However, once past that learning curve, the possibilities open up, and things become easier to understand and allow for further granularity.

Incentivized

I've not worked directly with IBM UrbanCode Deploy support. My DevOps team administers the environment and deals with that.

Incentivized

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

Incentivized

• we have had outages from Azure in the past

Incentivized

• Push button deployments.
• Consistency and ability to focus on other tasks.
• Required quite a bit of upfront customization with certain web deployments (WebSphere, etc.)
• Opened the door to other types of deployments and other automation.

Incentivized