Do More with Less: Automate and Accelerate Your Mainframe Application Release Cycle
Today, your mainframe needs to deliver new services at the same speed as the web and
mobile applications it supports, so building a robust cross-platform DevOps toolchain that lets you automate and accelerate your mainframe application release cycle is vital. A great example of this are the integrations between:
- Compuware ISPW to automate the promotion of code
- Compuware Topaz for Total Test to automate unit testing
- CloudBees Jenkins to drive Continuous Integration processes
- SonarSource SonarQube to use test metrics in Quality Gates and automatically regress failed code into ISPW to be fixed.
- XebaLabs XL Release to create, promote, regress, deploy and check the status of code releases through APIs
You can see a demo of this toolchain in “ISPW and Jenkins: A DevOps Integration Dream,” part of Compuware’s monthly “Did You Know?” webcast series:
Keep reading for a quick overview of how you can bring together some of the most robust mainframe and cross-platform DevOps tools available to seriously automate and accelerate your mainframe application release cycle.
Starting in ISPW, thanks to the visualization it provides, you can immediately see where your modules are based on simple shading to determine if another developer in another release path is working on the same code you are.
You could choose to move through your mainframe application release cycle in ISPW using manual processes, including generating and compiling code, promoting it to another level and having ISPW automatically handle deployments and generations, compiles of the changes developers make, behind the scene. But you can also automate that processes through ISPW REST APIs.
ISPW’s integration with Jenkins allows you to automate several things in your pipeline, including:
- Handling generates using APIs
- Promoting code to the next level
- Moving code down for analysis
- Running unit tests through Topaz for Total Test
Topaz for Total Test components can be managed by ISPW, enabling the migration of unit tests through the mainframe application release cycle to run specific tests for each level. After, you can pass the code to SonarQube to check against a quality gate if the code meets quality standards defined by your organization. Then you can pass the code to XebiaLabs XL Release, a robust pipeline management tool that automates, orchestrates and provides visibility into release pipelines.
In Jenkins, you can watch your pipeline progress. The first step is to generate the programs. When complete, you will get a job notification with a link you can click to see the exact outcomes and compile listing directly from the source code.
Back in ISPW, you will see the code progressing through the environments. In the Jenkins pipeline, you will see you’re getting the code for automated analysis. When you run your unit test through SonarQube and check it against the quality gate, if it fails, an API will be called that automatically regresses the code back to dev for its issues to be corrected.
In SonarQube, you can see which bugs were encountered in the problem and which were critical. After regression, whether you change to a more lenient quality gate or fix your code, once it passes the quality check and completes the Jenkins pipeline, it will trigger an XL Release project.
Once a developer tells XL Release that testing is complete, it handles the next task to promote the code to the stage level in ISPW. XL Release will move through the next set of steps for the promotion of code to production.
In ISPW, the status will show there is an approval required before you can move the code into production. This is accomplished simply by right-clicking in the lifecycle box next to the stage and selecting “Approve.”
Meanwhile, XL Release will be waiting for a response from ISPW through an API to ensure the approval has been completed. Once confirmed, XL Release will kick back in and promote the code to the production level. When the approval is accepted, the entire XL Release script will be completed as well.
Back in ISPW, you will see the code has successfully moved to production, all without the manual effort you would normally use to move code through your mainframe application release cycle.
Such is the power of a robust, mainframe-inclusive DevOps toolchain that allows you to integrate your modern Compuware mainframe tools with best-of-breed DevOps solutions. Through REST APIs, a developer can make changes in ISPW, go directly into Jenkins to kick off a pipeline and manage APIs doing quality scans, testing and even regression if quality gates aren’t met, followed by more testing steps and migration all the way to production.
Watch “ISPW and Jenkins: A DevOps Integration Dream” for more details on how the integrations help you automate and accelerate your mainframe application release cycle and build a modern mainframe-inclusive DevOps toolchain.