Azure Pipelines vs. BMC AMI DevX

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

I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.

Incentivized

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

Incentivized

• The tool I use is fairly intuitive. It doesn't take long to be using it full time.
• Changing the layout/view is fairly easy. This allows it to fit individual preferences.
• It is helpful to be able to view specific windows in full screen. Usually, I have it set up to view multiple windows, but sometimes, I just want to view one window in full-screen mode.
• the debug utility is very useful. Place stopping points is easy and one can set parameters as to when you stop at a line of code. Changing the data on the fly is easy and usefull. The interface is easy to use and make sense.

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

• Download source code plug-in on Azure DevOps to allow downloading prod version even if it's not in the assignment.
• Publishing Test Results on Azure DevOps from Total Test plugin
• Integration with DevEnterprise in Workbench and GenAI capabilities for enhance code analysis (Accross multiple programs/applications)

Incentivized

This is a very good range of tools that we use daily to maintain our programs

Incentivized

9 as it gives good smooth experience for all development tasks. Can be improved a little.

Incentivized

The tool is very reliable and we have had very few cases where we have had to contact support.

Incentivized

With one exception, we did not observe any slowdown in development activity when using the AMI DEVX Code DEBug tool.

Incentivized

Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes quickly.

Incentivized

The learning phase is relatively easy to implement.

Incentivized

The installation teams for these products have never complained about any difficulties during the integration of this range of tools into our IT system.

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

The names may have changed over the years, but anyone who has been around for a while will recognize them. For Software Configuration Management, I have used TSO/ISPF/SCLM, Panvalet, ChangeMan, Librarian, Endevor, and now Code Pipeline. All of them met the basic requirements. All of them had their advantages and disadvantages. Code Pipeline, however, stands head and shoulders above the rest in simplicity, completeness, effectiveness, efficiency, and elegance.

Incentivized

• we have had outages from Azure in the past

Incentivized

• Possitive impact. It is main product suite to enable devops in the mainframe applications team. All developers use these on day-to-day work.
• Negative impact: Recent usability issues caused disappointment in the application teams. It became hard motivate the development community to increase usage.

Incentivized