Pipelines Templates user guide
Organizations operating at scale need consistency to prevent chaos. If each development team in your organization is creating their own Pipelines according to their own sensibilities, that’s a recipe for disaster.
CloudBees Pipeline Templates give your organization the ability to enforce consistency. A small team can determine what Pipeline options are appropriate for your needs, and all of your development teams can choose from one of those options when they set up a software delivery project.
That way, your developers can focus on shipping product, and your organization can standardize the Pipelines they use to do it.
Pipeline Templates help ensure that Pipeline builds conform to organizational standards, and they work like this:
A small team (in this guide, we refer to this team as a shared services team) defines a Pipeline Template (or collection of Pipeline Templates) in a centralized Pipeline Template Catalog.
The shared services team, according to their policies and the organization’s needs, configures the Pipeline Templates in the Catalog to pre-define certain values and actions and/or leave room for customization.
When a development team is setting up a software delivery project, they build their Pipeline based on one of the Templates in the Pipeline Template Catalog.
Depending on how the shared services team configured the Template, the development team can customize certain options, while other options are pre-defined.
The developer user experience is streamlined in the pipeline template workflow.
Log in to the Team master or the managed master as an application developer.
Navigate to the folder where the job should be created.
In the side panel, click New Item.
Enter any unique values for the application pipeline. If the administrator has not configured any parameters in the template’s template.yaml file, then this secondary screen will not be shown.
Pipeline Templates are defined in Pipeline Template Catalogs, and both are stored in a source code repository.
Managing Pipeline Templates in source control has multiple benefits:
Configuration as code: The unique identifier and display name (within CloudBees Core) for the Catalog don’t have to be managed through the user interface.
Uniqueness: Because the Catalog is being defined in a single place, but applied both within and across CloudBees Core masters, it’s much easier to enforce uniqueness.
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 Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc.
Most CloudBees products are commonly referred to by their short names—Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake—throughout various types of CloudBees product-specific documentation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
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.