22 docs tagged with "template"

In Release, the phases in a template or release represent blocks of work that happen in succession.

This topic provides information about tasks in Release, which are the core components of activities within a template or release, logically grouped into phases.

This topic explains how to change the type of a task in Release, including the necessary permissions for modifying tasks in templates, planned releases, and active releases.

This topic provides an overview of the core concepts and processes in Digital.ai Release, including releases, phases, tasks, release flow, release owners, templates, and teams. It explains how Digital.ai Release helps plan, track, and execute releases, serving as a central source of truth for all involved stakeholders.

Using a Git trigger you can start a release that will execute an External Script task that contains a DSL. The External Script task should point to a file from a Git repository. You must provide HTTP/HTTPS access to the file with a direct link. HTTP authentication provides security.

Release triggers are an automated way to create and run a release. When you create a trigger for a release template and enable it, Release will execute the script associated with the trigger at a specified interval. When the trigger starts, it will create and start a new release from the template. A good example of a trigger is one that polls a source code management system like GitHub for a change and starts a release as a result.

You can use variables to manage information that you don't know in advance or that may change. Unlike global variables, release variables can only be used in the template or release in which they are created. You can create a release variable using the release flow editor or the Variables screen.

To use the Release REST API, you need to know the unique identifiers for templates, releases, phases and tasks. This topic explains where you can find them.

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

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.

You can configure the email notification preferences in Release by adding events that trigger notifications and by modifying the recipients that receive the email notifications.

The release flow editor shows the phases and tasks in the release. You can use this view to add, move, edit, and delete phases and tasks.

The Release planner view provides an interactive Gantt chart to view and edit the duration of the phases and tasks in a release or template. The Gantt chart is a combined timeline of the template or release, its phases, and the tasks within.

This topic covers Release properties, which are configurable attributes that influence the behavior and execution of a release.

The Release table view provides an alternative view of a template or release that is optimized for working with tasks.

This topic explains the structure of users, roles, and permissions in Release, focusing on how they ensure secure and efficient access control.

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.

The Release user interface includes multiple release planning and management views to accommodate all of the types of users that participate in the release process:

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

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

You can use the template version control feature to track changes to a template and to revert past changes. While Release automatically tracks template changes for compliance and auditing purposes, template version control is used to save specific versions of a template and to roll back changes.