AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
BMC AMI DevX
Score 9.0 out of 10
N/A
An enterprise ready, low-code Git-based DevOps toolchain that enables all developers to connect, transform and modernize mainframe application with CI/CD automation, integrated developer environments (IDE), AI/ML-based application performance monitoring and visualization dashboards, and automated testing.
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
I'm not sure what scenario it would not be suitable for. I have it up all day, though I do use the mainframe emulator to go back to the old 'green screen'. We have tools that we must use there. There is very little I can't do on the workbench. I'm trying to get some of our new developers to use it, as when I'm using it and talking to them on the phone, they don't know what I'm talking about.
We use CA Librarian here, and the workbench doesn't play well with that. I can't view the library my source is in; I have to copy it to a PDS.
I frequently make some copies of files on my own. I do each file at a time. The ability to create a macro to do all of them at once would be nice. Currently, I click the file and click 'copy to', then fill out the info for each file.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
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.
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
Optim is more user friendly in how it operates, in my opinion. It's less obtuse to figure out how to extract and mask the data required compared to File-AID. Further, Optim is easier to gather related tables, by far. I do prefer using File-AID via the Topaz GUI much more than using Optim via its GUI. Finally, I personally believe that File-AID is significantly faster to run than Optim - this could be a configuration issue.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
I can debug (expeditor) much faster and more efficiently. In fact, I was asked yesterday to run their job through Workbench Expeditor. I can also view data movement much better.
Code analysis lets me give a quicker explanation of what a program may do, as it provides a graphical interface showing processing and data movement.
