In part three of this video series, a developer's change set has been delivered to the development stream, and an integration build is needed in order to pick up the change set.
In this video Rational Developer for z Systems (RDz) and Rational Team Concert (RTC) will be used to:
- perform an integration build
- perform quality analysis on the build (zUnit & Code Coverage)
- prepare an Urban Code Deploy (UCD) package for deployment to a CICS region running on RD&T used for unit/function testing
Review ItemsIf you missed part one of this video series, it will help to review
DevOps for z using Rational Development and Test Environment for z Systems (RD&T): Video Series – Part 1 and the first video
Better DevOps on IBMz with Rational Development and Test Environment for z Systems (RD&T) - Part 1 which will show priming a RD&T environment from an existing mainframe environment using UCD.
If you missed part two of this video series, it will help to review
DevOps for z using Rational Development and Test Environment for z Systems (RD&T): Video Series – Part 2 and the second video
DevOps for IBMz with Rational Development & Test Environment (RD&T) - Part 2 which shows a developer implementing a development change set based on an enhancement request. The developer uses RDz + RTC to check out code, implement a change set, compile to RD&T, and run a debug session on the change code. This video uses items that were introduced in part two and it will help to review the zUnit, code coverage, and Integrating RDz Quality Analysis with RTC Builds sections.
Continuous IntegrationEven though this video shows only one change set being delivered, the intent of the video demonstration is to show the steps used when following "Continuous Integration" practices in software development.
Following "Continuous Integration" each developer develops code, perform code check-in, perform personal builds, run quality analysis (zUnit + Code Coverage) on their changed code, and then checks the results of their build. Once satisfied with their change set, the developer then delivers that code to the development stream.
In the background an integration build is set up on an automatic schedule (possibly multiple times a day, unlikely on a real mainframe but possible on RD&T), which will accept code changes that have been delivered to the development stream, perform an integration build on all of the changes, perform quality analysis on the build (zUnit + Code Coverage), and then publishes the build results for review.
Once the build has been reviewed, and has been approved for deployment into the test area for unit/function test, a package is created for Urban Code Deploy.
Integrating RTC and UCD to create the UCD PackageStarting with RTC V6.0 and UCD V6.1.1, users could set up RTC package definitions to create UCD packages. Here is the sample definition that was used in the video for creating the UCD package. It uses timestamp for versioning and an optional prefix to denote that this package is used for deploying to an RD&T CICS region.
For more information on how to integrate RTC and UCD, please visit the IBM Rational solution for Collaborative Lifecycle Management Knowledge Center:
https://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.0/com.ibm.team.build.doc/topics/c_deploy_with_UCD.htmlVideo SeriesToday's installment of this video series will show performing an integration build with quality analysis (zUnit + Code Coverage). Afterwards a UCD package is created with RTC in preparation for deployment for unit/function testing.
Please view the video here I will also post a final blog and video that describe completion of the scenario:
- Part 4 of this video series will show deploying a package for unit/function test with UCD using automated zUnit + code coverage analysis.