Posts Tagged ‘systems of engagement’

Compuware Brings Multi-Platform DevOps to the Z

January 19, 2018

The rush has started to DevOps for Z. IBM jumped on the bandwagon with an updated release of IBM Developer for z Systems (IDz) V14.1.1, which allows Z organizations to provide new capabilities and product maintenance to users sooner than the traditional release models they previously used from IBM.

Even more recently, Compuware, which described DevOps and the mainframe as the ultimate win-win, announced a program to advance DevOps on the mainframe with integrated COBOL code coverage metrics for multi-platform DevOps.  This will make it possible for all developers in the organization to fluidly handle multi-platform code, including mainframe code, in a fast delivery DevOps approach.

SonarSource-Compuware DevOps Dashboard

The new Compuware-SonarSource integrations are expected to ease enterprise DevOps teams trying to track and validate code coverage of COBOL application testing and do it with the same ease and employing the same processes as they do with Java and other more mainstream code. This ability to automate code coverage tracking across platforms is yet another example of empowering enterprise IT to apply the same proven and essential Agile, DevOps and Continuous Integration/Continuous Delivery (CI/CD) disciplines to both core systems-of-record (mainframe) as well as systems-of-engagement (mostly distributed systems).

Code coverage metrics promise insight into the degree to which source code is executed during a test. It identifies  which lines of code have been executed, and what percentage of an application has been tested. These measurements allow IT teams to understand the scope and effectiveness of its testing as code is moved towards production.

DevOps has become increasingly critical to mainframe shops that risk becoming irrelevant and even replaceable if they cannot turn around code improvements fast enough. The mainframe continues to be valued as the secure repository of the organization’s critical data but that won’t hold off those who feel the mainframe is a costly extravagance, especially when mainframe shops can’t turn out code updates and enhancements as fast as systems regarded as more inherently agile.

As Compuware puts it, the latest integrations automatically feed code coverage results captured by its Topaz for Total Test into SonarSource’s SonarQube. This gives DevOps teams an accurate, unified view of quality metrics and milestones across platforms enterprise-wide.

For z shops specifically, such continuous code quality management across platforms promises high value to large enterprises, enabling them to bring new digital deliverables to market, which increasingly is contingent on simultaneously updating code across both back-end mainframe systems-of-record and front-end mobile/web and distributed systems-of-engagement.

Specifically, notes Compuware, integration between Topaz for Total Test and SonarQube enables DevOps teams to:

  • Gain insight into the coverage of code being promoted for all application components across all platforms
  • Improve the rigor of digital governance with strong enforcement of mainframe QA policies for coding errors, data leakage, credential vulnerabilities, and more
  • Shorten feedback loops to speed time-to-benefit and more promptly address shortfalls in COBOL skills and bottlenecks in mainframe DevOps processes

Topaz for Total Test captures code coverage metrics directly from the source code itself, rather than from a source listing, as is the case with outdated mainframe tools. This direct capture is more accurate and eliminates the need for development, Compuware reported.

The new integration actually encompasses a range of tools and capabilities. For instance:

From within a Compuware Xpediter debug session, a developer can kick off a Compuware Topaz for Total Test automated unit test and set it up to collect code coverage info as it runs. Code coverage metrics then can be automatically fed into SonarSource’s SonarQube where they can be displayed in a dashboard along with other quality metrics, such as lines going to subprograms.

It also integrates with Jenkins as a Continuous Integration (CI) platform, which acts as a process orchestrator and interacts with an SCM tool, such as Compuware ISPW, which automates software quality checks and pushes metrics onto SonarQube among other things. ISPW also is where code gets promoted to the various stages within the lifecycle and ultimately deployed. Finally Topaz is Compuware’s Eclipse-based IDE from which developers drive all these activities.

The Compuware announcement further delivers on its promise to mainstream the mainframe; that is, provide a familiar, modern, and intuitive multi-platform mainframe development environment—integrated with state-of-the-art DevOps tools for veteran mainframe developers and, more importantly, those newly engaged as IT newbies from the distributed world. In short, this is how you keep your Z relevant and invaluable going forward.

** Special note regarding last week’s DancingDinosaur reporting on chip problems here; Don’t count on an immediate solution coming from the vendors anytime soon; not Google, IBM, Intel, AMD, ARM, or others. The word among chip geeks is that the dependencies are too complex to be fully fixed with a patch. This probably requires new chip designs and fabrication. DancingDinosaur will keep you posted.

DancingDinosaur is Alan Radding, a veteran information technology analyst, writer, and ghost-writer. Please follow DancingDinosaur on Twitter, @mainframeblog. See more of his IT writing at technologywriter.com and here.

IBM Brings Cloud DevOps to the Mainframe

December 3, 2014

Is your organization ready for DevOps?  It should be coming to System z data centers almost any day now, riding in on newly announced IBM cloud-based DevOps services, software, and infrastructure designed to help large organizations develop and deliver quality software faster.

IBM Launches Bluemix Garage at London's Level39

Launch of the Bluemix Garage in London

DevOps streamlines enterprise workflow by truncating the development, testing, and deployment process. It entails collaborative communications around the end-to-end enterprise workflow flow and incorporates a continuous feedback to expedite the process. DevOps evolved out of Agile methodologies over a decade ago.

Agile was intended to streamline the traditional waterfall IT development process by putting developers and business unit people and the deployment folks together to build, test, and deploy new applications fast. Agile teams would deliver agreed upon and tested functionality within a month. Each deliverable was short, addressing only a subset of the total functionality. Each was followed by the next containing yet more functionality. In the process, previously delivered functionality might be modified or replaced with a new deliverable.

IBM is streamlining the process further by tapping into the collaborative power of the company’s Cloud portfolio and business transformation experience to speed the delivery of software that supports new models of engagement.  To be clear, IBM definitely is not talking about using DevOps with the organization’s systems of record—the core transaction systems that are hallmark of the z and the heartbeat of the enterprise. The most likely candidates will be systems of engagement, systems of innovation, and analytics systems.  These are systems that need to be delivered fast and will change frequently.

According to IBM software-driven innovation has emerged as a primary way businesses create and deliver new value to customers. A survey of 400 business and IT executives by the IBM Institute for Business Value showed businesses that are more effective at software delivery are also more profitable than their peers nearly 70 percent of the time. DevOps provides a way for businesses to remain competitive, applying lean and agile principles to software development to speed the delivery of software that meets new market requirements.

Agile represented a radical departure from the waterfall process, which called for developers to take a full set of business requirements, disappear to two years, and return with a finished application that worked right.  Except that it often took longer for the developers to return with the code and the application didn’t work as promised. By then the application was well over budget and late.  System z shops know this well.

DevOps today establishes a continuous, iterative process flow between the development team and the deployment group and incorporates many Agile concepts, including the active involvement of the business people, frequent testing, and quick release cycles. As the IBM survey noted  DevOps was spurred by the rise of smartphones and mobile computing. Mobile users demand working functionality fast and expect frequent updates. Two-year release cycles were unacceptable; competitors would be out with newer and better apps long before.  Even six-month release cycles seem unresponsive. This is one of the realities DevOps addresses.  Another reality is extreme scaling, something z data centers understand.

According to IBM, the company’s new DevOps Innovation Services help address the challenge of scaling development, enabling enterprises to shorten their software delivery lifecycle. The hybrid cloud services combine IBM’s industry expertise from hundreds of organizational change and application development projects with the industry’s leading application development portfolio, especially Bluemix, IBM’s open DIY cloud PaaS platform. They also apply the flexibility of IBM’s enterprise-grade, hybrid cloud portfolio, which was recently ranked by Synergy Research Group as the leading hybrid and private cloud for the enterprise. These services are based on SoftLayer, IBM’s cloud infrastructure platform.

In a second DevOps-related announcement last month IBM described an initiative to bring a greater level of control, security and flexibility to cloud-based application development and delivery with a single-tenant version of Bluemix. The new initiative enables developers to build applications around their most sensitive data and deploy them in a dedicated cloud environment to help them capture the benefits of cloud while avoiding the compliance, regulatory and performance issues that are presented with public clouds. System z shops can appreciate this.

Major enterprise system vendors like IBM, EMC, Cisco, and Oracle are making noises about DevOps. As far as solid initiatives IBM appears far ahead, especially with the two November announcements.

DancingDinosaur is Alan Radding, an independent IT analyst and writer. Follow DancingDinosaur on Twitter, @mainframeblog. Find more of his IT writing at Technologywriter.com and here.


%d bloggers like this: