Overview of Jenkins architecture

The BMC AMI DevOps Jenkins plug-ins (hpi) consist of two plug-ins (BMC AMI DevOps Common and BMC AMI DevOps Schema Management for Db2) installed on a Jenkins controller. The BMC AMI DevOps plug-in steps are defined in Jenkins projects or pipelines. The Jenkins controller runs the AMI DevOps plug-in steps to perform the required operation as defined in the project or pipeline configuration.

Related topics

Getting started

 

Architecture diagram DevOps.drawio (2).png

This process involves the following steps:

  1. Run the Jenkins project or pipeline by committing any change in the Git repository file or local file system file, via a trigger or manual run.
  2. The Jenkins automation controller gets any project or pipeline supporting files from the Git repository or local file system.
  3. The Jenkins automation controller manages the tasks and steps defined in the project or pipeline.
  4. The Jenkins automation controller runs the authentication step for communication with the z/OSMF server.
  5. The Jenkins controller runs the AMI DevOps plug-in steps to perform the required operation defined in the project or pipeline configuration. 

 

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