Source Code Management
Without an Agile source code management (SCM) tool, you can’t effectively keep track of work in progress, maintain a chain of command, use separate environments for testing or fully support the software development lifecycle, among other basic processes. While elaborate in-house SCM solutions and even some of the most complex, antiquated vendor tools can help you accomplish these essential tasks, mainframe shops need evolve to meet new demands in a digital economy—so too must their SCM tools.
Compuware’s Agile SCM solution leverages the strengths of ISPW—including integrations with several Compuware mainframe tools as well as many cross-platform distributed DevOps tools—enabling developers to quickly and safely build, test and deploy mainframe code using several modern capabilities.
Like all of your mainframe tools, your SCM tool must integrate into your enterprise’s overall DevOps process, enabling you to automate the compiling, testing and promotion of code. Integrations with Jenkins, XebiaLabs and REST APIs for ISPW enable users to create, promote, deploy and check the status of code releases using popular Agile/DevOps tools.
Webhooks complement APIs by automatically providing data to applications, services and DevOps tools when workflow events have been triggered. In ISPW Webhooks, you can:
Waiting in line behind other developers to make code changes is a poor development practice when mainframe teams need to be working in Agile two-week sprints. Mainframe teams must develop and deliver faster. ISPW’s multiple development areas enable parallel development. Additionally:
Most SCM tools look for code change impacts at the time of compiling. That’s too late to discover your change to one program affects every program to which it relates. You need to see how changes will cascade before compiling to get a true sense of how big or small a project will be and to plan accordingly. ISPW lets developers see how a potential code change impacts the rest of the mainframe environment early on using graphical charting.
Most SCM tools only allow developers to compare program versions in ISPF, but this environment makes it hard to spot and easily merge changes. ISPW’s side-by-side compare through Topaz Workbench, Compuware’s Eclipse-based IDE and modern development interface, makes it easy to pinpoint differences between program versions and make smart merging decisions.
In an age that demands agile responsiveness for customers, code approvals can’t be delayed by an absent manager or team member. ISPW’s mobile interface eliminates delays by enabling approvers to respond to alerts anywhere, anytime code changes are ready for approval.
Unlike other SCM tools, ISPW is much easier to set up and administer. Requiring less custom coding through processors, development teams need only select the specific pre-coded capabilities they want to use. In another example, ISPW uses modular, reusable compile skeletons for simple substitution, nesting and conditional pathing. With a few skeletons, you can cover a wide range of compiles, from COBOL to Db2 and more. And because skeletons substitute version libraries, they rarely need to be changed.
Mainframe SCM can’t be an island because it’s so integral to other development activities. ISPW integrates into core Compuware products through Topaz Workbench to enable: