...
| Table of Contents |
|---|
Topology Components
Jenkins Host: Where the Jenkins controller (providing build/deploy services as part of ALM) is run
...
The MettleCI Workbench application running on your DataStage Engine tier needs to perform a dynamic lookup of Work items when displaying the Git Commit page.
The MettleCI Workbench application running on your DataStage Engine tier needs to commit to your Git platform.
The Jenkins Host and your Git repository need to communicate in order to configure Git commits to automatically trigger Jenkins pipelines. Jenkins then needs access to your Git repository to source the artefacts for build and deployment. The Jenkins pipeline definitions ('Jenkinsfiles') are themselves stored and managed in a Git repository.
The Developer Workstation provides data engineers with access to your ALM tools' user interfaces via a supported web browser.
The Developer Workstation provides data engineers with access to your Jenkins user interfaces via a supported web browser.
The Developer Workstation provides a DataStage client tier with access to the development environment's DataStage Engine and Services tiers.
Your Jenkins pipeline perform their duties via an agent installed on the MettleCI Host.
The MettleCI Host requires regular access to the development environment's DataStage Engine and Services tiers, identical to that of Developer Workstations.
The MettleCI Host requires regular access to the downstream test environments' DataStage Engine and Services tiers, to affect automated deployment.
Using Multiple Engines with Multiple Jenkins Agents
In real-world scenarios it’s possible that security restrictions or network zoning prohibit a single MettleCI Agent Host
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The diagram above (explained in more detail on this page) describes how you might deploy Jenkins Agents in complex multi-environment DataStage topologies.
This example employs multiple environment-specific MettleCI Agent hosts, each featuring a dedicated Jenkins Agent
This is by no means the only way to support multiple DataStage environments, but is certainly one of the easiest solutions to understand and maintain.