Simple Shared Library example

This pipeline executes the following steps after a developer has promoted their code in Code Pipeline:

  • Retrieve the mainframe code from Code Pipeline for later analysis by SonarQube.
  • Retrieve Total Test test definitions for the corresponding Code Pipeline application from GitHub.
  • Execute those test scenarios that belong to the COBOL programs that have been promoted.
  • Retrieve the Code Coverage metrics generated during test execution from the mainframe repository.
  • Pass all information (sources, test results, code coverage metrics) to SonarQube.
  • Receive a Sonar quality gate webhook callback and analyze the status of the quality gate.
  • If the quality gate was passed, continue the process by triggering an XL Release template.
  • In either case (passed/failed), send an email to the developer informing them of the status of the pipeline.

Related topics

Combined-scenario

Synchronization-of-Git-to-Code-Pipeline

Shared-Library-Pipelines

Advanced-Pipelines

Comparing the code in this example to the basic example pipeline you will find that they differ only in a few, minor details. One of the differences being that the "hard coded" configuration parameters are externalized into a configuration .yml file, allowing for changes in configuration without having to change any pipeline code.

Example
Mainframe_CI_Pipeline_from_Shared_Lib



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*