DevOps Lifecycle – Build

Use ISPW to prepare applications to test or deploy to production with familiar Eclipse-based interface

  • Generate feature pulls in correct copybooks, compiles program, and links it to correct library
  • Use standard JCL within ISPW to initiate compiles and links, confining all development activities to one environment for heightened visibility and sustained control
  • Use Promotion Analysis to automatically identify dependencies so that components can be confidently deployed
  • Leverage Source Code Downloader Jenkins plugin to download source code stored in ISPW into Jenkins for code quality analysis and reporting by SonarSource’s SonarQube
  • Use ISPW Operations Jenkins plugin to build DevOps pipelines in Jenkins to manage code throughout development lifecycle and easily orchestrate ISPW operations, such as generate, promote, compile, deploy on the mainframe, or pull in source code from Git, all within Jenkins pipelines
  • Use ISPW for mainframe source code management (SCM), build, and deploy, or leverage Enterprise Git, such as Bitbucket or GitHub, for source control and ISPW for build and deploy
  • Trigger ISPW operations with Release or CloudBees Flow or use REST APIs to integrate with tools of choice

Use COPE to build virtual development and testing environments for IMS applications

  • Transform physical resources for stages of application development and testing into virtualized, extensible representation of same set of physical resources
  • Enable developers to uniquely work independently without disruption