19 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 from a Git repository.

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.

Release variables are scope-specific configuration elements that help manage dynamic values within your release templates and instances. Unlike global variables, release variables are confined to the template or release where they are created.

Teams are used to group one or more users in Release. Folder, template, or release-level permissions can be assigned to one or more teams.

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, workflows, configurations, and dashboards by project, team, or any other model that fits your organization. With folders, you can apply security settings to many assets at once using 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.

The Flow Editor shows the phases and tasks in a release or a template. 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.

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.

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.