22 docs tagged with "template"

In Release, the phases in a template or release represent blocks of work that happen in succession. To add a phase to a template or release, use the release flow editor.

In Release, the activities in a template or release are modeled as tasks, which are logically grouped in phases.

To change the type of a task in a template, you need the Edit Template permission on the template. To change the type of a task in a release, you need the Edit Task permission on the release.

Digital.ai Releases are at the heart of Digital.ai Release. A release represents a number of activities in a certain time period, with people working on them. Digital.ai Release allows you to plan, track, and execute releases automatically. It acts as a single source of truth for everyone who is involved in making the release a success.

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.

You can use templates to model the ideal process of a release flow. You can import a template from:

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. To go to the release flow editor view, open a template or a release and select Release flow from the Show menu.

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.

To specify metadata for a release or template, select Properties from the Show menu to go to the release properties page.

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

Users refer to individuals who are authorized to access the Release. In order to log into the Release, users must provide valid credentials such as username and password. This is a security measure to ensure that only authorized individuals have access to the system and its data.

In Release, templates are like blueprints for releases. You 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.

You can create a release from a template using these methods:

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.