Defining Template Catalogs for Team Masters

  1. Log in to CloudBees Core Operations Center as an administrator or team administrator.

  2. Navigate to the Team.

  3. On the team’s master, 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 CloudBees Core 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, repo for the catalog.

  6. Select Save to create the catalog in CloudBees Core and to begin importing it.

Copyright © 2010-2019 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center and DEV@cloud are trademarks of CloudBees, Inc. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.