Defining Pipeline Template Catalogs

1 minute read

Defining Template Catalogs for team controllers

  1. Log into operations center as an administrator or team administrator.

  2. Navigate to the Team.

  3. On the team’s controller, in the side panel, select Pipeline Templates.

  4. In the side panel, select Add catalog.

  5. Enter:

    1. Branch or tag from the repository to use for this catalog.

    2. How often the repository should be queried to find if there are updates to the template.yaml and Jenkinsfile files.

    3. Type of source control: git, github, or mercurial.

    4. Credentials, username, or repository for the catalog. For example, use the CloudBees examples repository.

      For this repository to work with Template Catalogs, copy it to a separate top-level repository.
    5. Select Save to create the catalog and to begin importing it.

Defining Template Catalogs for managed controller

  1. Log in as an administrator.

  2. In the side panel, click Pipeline Templates.

  3. In the side panel, click Add catalog.

  4. Enter:

    1. Branch or tag from the repository to use for this catalog.

    2. How often CloudBees CI should query the repository to find if there are updates to the template.yaml and Jenkinsfile files.

    3. Type of source control: git, github, or mercurial.

    4. Credentials, username, or repository for the catalog. For example, use the CloudBees examples repository.

      For this repository to work with Template Catalogs, copy it to a separate top-level repository.
    5. Click Save to create the catalog in CloudBees CI and to begin importing it.