A Pipelines user can view and manage lifecycle staging of each template version. In addition, a user can view the YAML and documentation for each template source.
Managing Templates
Pipelines users can view the catalog of successfully loaded templates, and manage lifecycle staging of each template version.
Viewing Templates
From the Application tab go to Pipelines | Reusables, and select the Templates tab to view the list of templates.
Property | Description |
|---|---|
Name | The named type of the template. |
Versions | The current version of the template. |
In Use By | Shows the numberof pipelines that are using the template |
Released at | The date and time when the template was released. |
Releasing Template Versions (1.38 and lower)
When a template is added, it is added as the latest version of the template. However, whenever the template source syncs, the latest template can change. If you want to keep a specific version of a template, you have the option of releasing that version of the template.
A template that has been properly Git tagged with semantic version information can be formally released. When a template is released, it can be referenced by its version number. That version of the template continues to be available even after a new latest version has been synced from the template source.
Note
After a version of a template is released, it cannot be changed. If any changes are to be made, a new release should be created.
To release the latest version of a template:
Go to your Github repository and perform these steps:
In Github, go to the templates repository.
Note
System template files should be stored in the template source repository in a specific order for them to be uploaded to Pipelines. For more information, see Structure of Template Source Repository.
Click Releases.
Click Draft a new release.
In the page that appears, click the Tag version field and enter a git tag using the format:
<template_namespace>/<template_name>@<semver>.The format of <
semver>must be compliant with the semantic versioning standard (Major.Minor.Patch).Example:
jfrog/foo@1.1.1.