Pipelines users can view the catalog of successfully loaded templates, and manage lifecycle staging of each template version.
From the Application tab go to Pipelines | Extensions & Templates, and select the Templates tab to view the list of templates.
|The named type of the template.|
|The current version of the template.|
|The success/failure status of the last sync.|
|The namespace of the template.|
|The date and time when the template was released.|
|The date and time when the template was retired.|
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.
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:
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.
semver>must be compliant with the semantic versioning standard (Major.Minor.Patch).
To view version logs:
Administrators can retire template versions, making them unavailable for further use. You can select an advance date for a version's retirement. When a template version is retired, pipeline sources using the retired version should be updated to use a different version of the template.
To retire a template version:
The Retired At column is updated to show the retirement date.
To view the Template Definition and Values Example YAML:
Either right-click or hover over the rightmost region of the row where the template version is listed to reveal the Actions, and click View YAML from the drop-down list.
If you included a readme file along with your template files, you can view the contents of this file. To do this, either right-click or hover over the rightmost region of the row where the template is listed to reveal the Actions icon, and click Documentation.
A Template Source represents a source control repository (such as GitHub or BitBucket) where Pipelines template definition files can be found. A template source connects to the repository through an administration integration.
After a template source is added, Pipelines automatically loads all template definition files from that repository and its subdirectories.
Prerequisites for Template Sources:
To add a Template Source:
Pipelines then syncs the template source to load the templates.
To view the the list of configured template sources, from the Application tab go to Pipelines | Extensions & Templates, and click the Sources tab.
The tab displays the list of configured template sources that Pipelines will load templates from.
Each row of the template sources list includes the following:
|The source repository path of the template source|
|The source repository branch|
|The success/failure status of the last sync|
|The time and date of the last sync|
|The username of the VCS user who made the triggering change|
|The commit SHA that triggered the last sync|
|The source type|
When any of the pipeline config files have changed, you may need to manually sync the pipeline source to reload. To do this:
If the Latest Status indicates that the sync failed, click Logs to view the logs of all synchronized files.