These pipelines are in standard tekton format. They can be found in ./pac/pipelines and ./pac/tasks.
Depending on the use case there are two ways of consuming of the RHTAP pipeline:
For this scenario, the RHTAP pipeline definition can be directly referenced from the official repository. In such case, all the updates and security pathes provided will be available immediately to the consuming pipelines. No actions required from the consumer side.
In the pipelines as code runners, you can find the reference to these pipelines in the following format. See a full pipeline runner example here
pipelinesascode.tekton.dev/pipeline: "raw-url-with-branch/pac/pipelines/docker-build-rhtap.yaml"
pipelinesascode.tekton.dev/task-0: "raw-url-with-branch/pac/tasks/init.yaml"
The placeholder raw-url-with-branch would have a reference to the original pipelines repository or a forked versions in raw reference format, or blob format for github enterprise.
https://raw.githubusercontent.com/redhat-appstudio/tssc-sample-pipelines/v1.2.x
To track the latest pipelines (1.2.x or 1.3.x) you can use the x branches in the following form. The x versions will match the latest 1.minor release. For example if 1.2.0, 1.2.1, 1.2.2 exist 1.2.x will match the 1.2.2. To pin your usage to an older release choose the specific version you would like.
If any customization to the default RHTAP pipeline definition is needed or immediate updates are not desired, workflow described in this section should be taken.
Fork this repository and modify the default RHTAP pipeline definition according to your needs. Reference the modified version of the pipeline.
Replace raw-url-with-branch would have a reference to the original pipelines repository or a forked versions in raw reference format, or blob format for github enterprise. The tssc-sample-templates consumer of this will do this automatically when regenerating the templates with updated piplines.
https://raw.githubusercontent.com/MY_ORG/tssc-sample-pipelines/v1.3.x
To consume CVE fixes and pipeline updates in the upstream, one should rebase changes in the fork on top of the new RHTAP pipeline version. You can validate these in a branch before rolling out to your internal users.
Modify the template placeholders to match your backstage template vars
Note, PaC also has {{variables}} and you should not modify those.
{{values.appName}} -> ${{ values.appName }}{{values.dockerfileLocation}}-> ${{ values.dockerfileLocation }}{{values.namespace}}-> ${{ values.namespace }}{{values.image}}-> ${{ values.image }}{{values.namespace}}-> ${{ values.namespace }}{{values.buildContext}}-> ${{ values.buildContext }}{{values.repoURL}}-> ${{values.repoURL}}