Define Pipeline Template Catalogs

2 minute read

Define Pipeline Template Catalogs for team controllers

Starting with the July 2026 CloudBees CI release, Blue Ocean and team controllers will reach end-of-life (EOL) and will no longer be supported. After this date, Blue Ocean and team controllers will not receive updates, security patches, or technical support and will be removed from the CloudBees Assurance Program (CAP).

What this means for you:

  • Team controllers will cease to function starting with the July 2026 release.

  • Blue Ocean may continue to work, but is no longer supported by CloudBees.

  • No further updates or security patches will be provided.

  • Technical support for Blue Ocean and team controllers will no longer be available.

CloudBees strongly encourages all customers to complete their migration away from team controllers before the EOL date to ensure uninterrupted service. For detailed migration guidance, please refer to In-place conversion of team controllers to managed controllers. If you have questions or need assistance, please contact CloudBees Support.

  1. Sign in to the 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 Template Catalogs.

  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 or github.

    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.

Define Pipeline Template Catalogs for managed controller

  1. Sign in as an administrator.

  2. In the side panel, select Pipeline Template Catalogs.

  3. In the side panel, select 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 or github.

    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 in CloudBees CI and to begin importing it.