Release Folders and Templates

In Release, templates are like blueprints for releases. You can use templates to model the ideal process of a release flow. A template can describe a procedure that is used to deliver different applications, or it can describe a procedure that is used to release a particular application and that will be reused for different versions of the application.

This topic explains how to use templates to model the ideal process of a release flow.

This topic describes how to create a release from a template using various methods and the steps required before starting the release.

Folders provide an intuitive way to organize your templates, releases, configurations and dashboards by project, by team, or by any other model that fits your organization. With folders, you can easily apply security settings to a large number of templates and releases by setting role-based access control at any level of your folder hierarchy.

This topic describes how you can migrate existing templates from earlier versions of Release into folders. It shows an example in which all templates related to releasing the Release product will be moved to a folder called Release.

GitOps-enabled Folder Versioning

Template version control has been replaced by GitOps-enabled folder versioning. We recommend using GitOps-enabled folder versioning to manage templates, variables, connections, and other entities.

You can use the Release Releasefile view to see the current template in Releasefile format.