Create a build pipeline
Open your project, select the Pipelines entry and create a New pipeline. Azure DevOps pipelines assume that they are connected to a source repository. Therefore, you will be asked to point to the repository storing your code. In a mainframe situation this is likely not a repository storing mainframe code, but still you can connect the pipeline to the repository storing Total Test projects. The selection process will depend on the specific SCM you choose. For example, when using GitHub, the dialog will list all GitHub repositories you have been active recently as a contributor.
Once connected to the repository (you may be asked for permission to use Azure DevOps for the GitHub repo) select the Starter pipeline, since we will build the yaml file (describing the pipeline) from scratch and not use an existing one.
Define pipeline specific variables / parameters
In addition to the variables from the group mainframe-pipeline-parameters, the pipeline uses the following variables. Define them by clicking the Variables button in the pipeline definition. As with the variable group, you can and should define some variables a secret.
Variable | Description | Secret Value |
|---|---|---|
azureRestAuthorization | authorization header for the http request (including the 'Basic ' part of the header), i.e. your encrypted Azure DevOps PAT. | Y |
ispwApplication | Code Pipeline application (passed into the process by the Code Pipeline webhook) | N |
ispwContainerName | Code Pipeline container name (passed into the process by the Code Pipeline webhook) | N |
ispwContainerType | Code Pipeline container type (passed into the process by the Code Pipeline webhook) | N |
ispwLevel | Code Pipeline level (passed into the process by the Code Pipeline webhook) | N |
Create pipeline yaml
You may use the example pipeline yaml file, which we will describe in detail, below, as a starting point and adapt to your needs. Refer to the Azure DevOps documentation for details on how to define the pipeline elements.