With IBM Dependency Based Build (DBB) 1.0 announced in March 2018, IBM removed the last impediment preventing the ability to bring z/OS artifacts into a platform-agnostic open source pipeline.
Earlier in 2017 Rocket Software led the way by porting on z/OS git, the world’s most widely-used version control system, which is a critical component for many companies’ DevOps transformation, mainly thanks to its strong support of parallel development.
DBB completes this offering by providing traditional z/OS applications with build automation capabilities that can be integrated in a DevOps pipeline using Jenkins Continuous Integration or another pipeline coordinator.
These capabilities rely on the Apache Groovy scripting language, known for its concise, readable and expressive syntax, easy to learn for Java developers and seamlessly integrating with third party tools.
The diagram above shows how this first set of features serve the wider vision of supporting an open source Devops pipeline that includes traditional z/OS artifacts :
â€˘ Editing z/OS artifacts and access to the host provided by IBM Developer for Z Systems (IDz EE) which includes a new feature to trigger DBB build.
â€˘ EGit plugin enabling the integration with git version control which can pull from any git server such at GitHub.
â€˘ SonarQube code review operations which can be triggered either from IDz or Jenkins.
â€˘ CI / CD operations orchestrated by Jenkins invoking Groovy scripts then DBB APIs, then Unit Tests performed by XaTester in this setup example, and finally deployment operations controlled here by UrbanCode Deploy.
â€˘ Surrounded with dotted lines are areas where we continue to focus. Migration is possible today with the existing zImport capability, but we want to provide additional features to make it easier to migrate the build process itself. We are currently investigating for future releases integration to software repositories such as Nexus and Artifactory.