Define Variable group
Variable groups allow defining and storing default values that can be used by more than one pipeline. Using variable groups saves from having to define the same variables over and over again. The example uses a variable group. Such a group can be defined by selecting your project, clicking the Pipeline selection on the left and selecting the Library option.
The example uses a variable group named mainframe-pipeline-parameters and contains the following variables. Some of these variables are defined as secret making them invisible both in the interface as well as in the execution logs.
Name | Description | Secret |
|---|---|---|
agentScriptsPath | Folder containing the PowerShell-scripts on the machine the agent executes on | N |
azureOrganization | Azure DevOps organization this variable group belongs to | |
azureRestAddress | Base URL for the use of the Azure DevOps REST API | N |
ccRepo | Code Coverage repository to use | N |
ccTestId | Code Coverage test id to use | N |
cesToken | CES token to be used for Code Pipeline Rest API calls | Y |
cesUri | The URL for CES | N |
cliPath | Location of the Workbench CLI in the machine the local agent executes on | N |
gitProject | Git(Hub) project that the pipelines are connected to (storing the Total Test projects) | N |
hostCodePage | Mainframe code page in use | N |
hostPassword | Host password | Y |
hostPort | TCP port HCI is communicating on | N |
hostUri | Host name or IP address of the mainframe LPAR to connect to | |
hostUser | Host (TSO) user id to logon to the mainframe | Y |
ispwConfig | Code Pipeline configuration | N |
ispwServer | Code Pipeline Server (usually same as ispWConfig) | |
releaseDefinitionId | Azure DevOps internal id of the release pipeline definition | |
sonarAuthorization | authorization header for the http request (including the 'Basic ' part of the header), i.e. SonarQube access token encrypted similarly to the Azure PAT | |
sonarScannerPath | Folder containing the Sonar Scanner installation on the machine the local agent executes on | |
sonarServer | URL for the SOnarQube server | |
tttEnvironment | Id for a Total Test Functional Test environment, to execute functional test scenarios | |
workspaceRoot | Folder on the machine the local agent executes on, to be used as workspace during pipeline execution |