Pipelines as Code command reference

Pipelines as Code command reference
Splitting Pipelines as Code logs by namespace
Additional resources

You can use the tkn pac CLI tool to control Pipelines as Code. You can also use the oc command to view Pipelines as Code logs.

The tkn pac CLI tool offers the following capabilities:

Bootstrap Pipelines as Code installation and configuration.
Create a new Pipelines as Code repository.
List all Pipelines as Code repositories.
Describe a Pipelines as Code repository and the associated runs.
Generate a simple pipeline run to get started.
Resolve a pipeline run as if it was executed by Pipelines as Code.

You can use the commands corresponding to the capabilities for testing and experimentation, so that you don’t have to make changes to the Git repository containing the application source code.

Basic syntax

$ tkn pac [command or options] [arguments]

Global options

$ tkn pac --help

Utility commands

bootstrap

Table 1. Bootstrapping Pipelines as Code installation and configuration
Command	Description
`tkn pac bootstrap`	Installs and configures Pipelines as Code for Git repository hosting service providers, such as GitHub and GitHub Enterprise.
`tkn pac bootstrap --nightly`	Installs the nightly build of Pipelines as Code.
`tkn pac bootstrap --route-url <public_url_to_ingress_spec>`	Overrides the OpenShift route URL. By default, `tkn pac bootstrap` detects the OpenShift route, which is automatically associated with the Pipelines as Code controller service. If you do not have an OpenShift Container Platform cluster, it asks you for the public URL that points to the ingress endpoint.
`tkn pac bootstrap github-app`	Create a GitHub application and secrets in the `openshift-pipelines` namespace.

repository

Table 2. Managing Pipelines as Code repositories
Command	Description
`tkn pac create repository`	Creates a new Pipelines as Code repository and a namespace based on the pipeline run template.
`tkn pac list`	Lists all the Pipelines as Code repositories and displays the last status of the associated runs.
`tkn pac repo describe`	Describes a Pipelines as Code repository and the associated runs.

generate

Table 3. Generating pipeline runs using Pipelines as Code
Command	Description
`tkn pac generate`	Generates a simple pipeline run. When executed from the directory containing the source code, it automatically detects current Git information. In addition, it uses basic language detection capability and adds extra tasks depending on the language. For example, if it detects a `setup.py` file at the repository root, the pylint task is automatically added to the generated pipeline run.

resolve

Table 4. Resolving and executing pipeline runs using Pipelines as Code
Command	Description
`tkn pac resolve`	Executes a pipeline run as if it is owned by the Pipelines as Code on service.
`tkn pac resolve -f .tekton/pull-request.yaml \| oc apply -f -`	Displays the status of a live pipeline run that uses the template in `.tekton/pull-request.yaml`. Combined with a Kubernetes installation running on your local machine, you can observe the pipeline run without generating a new commit. If you run the command from a source code repository, it attempts to detect the current Git information and automatically resolve parameters such as current revision or branch.
`tkn pac resolve -f .tekton/pr.yaml -p revision=main -p repo_name=<repository_name>`	Executes a pipeline run by overriding default parameter values derived from the Git repository. The `-f` option can also accept a directory path and apply the `tkn pac resolve` command on all `.yaml` or `.yml` files in that directory. You can also use the `-f` flag multiple times in the same command. You can override the default information gathered from the Git repository by specifying parameter values using the `-p` option. For example, you can use a Git branch as a revision and a different repository name.

Splitting Pipelines as Code logs by namespace

Pipelines as Code logs contain the namespace information to make it possible to filter logs or split the logs by a particular namespace. For example, to view the Pipelines as Code logs related to the mynamespace namespace, enter the following command:

$ oc logs pipelines-as-code-controller-<unique-id> -n openshift-pipelines | grep mynamespace (1)

1	Replace `pipelines-as-code-controller-<unique-id>` with the Pipelines as Code controller name.

Pipelines as Code command reference