The following diagram is one possible configuration, and is presented as an example for further architecting. The number of IS environments, for example, and how many tiers they use, is notional
Connection descriptions
# | Summary | Description | Technical |
|---|---|---|---|
1 | MettleCI Workbench Service (Engine Tier) ↔︎ Your Work item Management system | The MettleCI workbench is configured to perform a dynamic lookup of work items as part of the Git Commit process. Currently supported work item management systems are listed here. | The Workbench service on your DataStage Engine tier needs to be able to use your Work Item Management system’s query API, over whatever protocols/ports it requires. |
2 | MettleCI Workbench Service (Engine Tier) ↔︎ Your Git Repository | ||
3 | Jenkins Host ↔︎ Your Git repository | Jenkins can keep pipeline definitions (as jenkinsfile files) in a repo so they can be versioned the same as the artifacts | |
4 | Jenkins Host ↔︎ DataStage designer client (developer workstation) | Web access to Jenkins by developers | |
5 | Jenkins Host ↔︎ DataStage designer client (MettleCI host) | Jenkins controller issues commands to the Jenkins Agent to perform MettleCI related tasks such as code movement, and DataStage deployment (project manipulation, job compliation) | |
6 | Developer Workstation ↔︎ IS/DS Service/Engine tiers | Normal developer activity such as editing jobs, test compilations, etc | |
7 | |||
8 | |||
9 | |||
10 |