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.
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.
You can use variables to manage information that you don't know in advance or that may change.
This topic demonstrates how to use a Jython Script task in Release to extract a value from a key-value map release variable and store it in another variable.
You can use variables to manage information that you don't know in advance or that may change.
This tutorial will show you how to use the extended variable mechanism to create a release that retrieve a list a of issues from Atlassian JIRA, ask a user to revise the list, and update the issues in JIRA
This topic explains how to define configuration objects in Release to store and manage settings used across multiple tasks. Examples include storing connection information for Jenkins, JIRA servers, or remote hosts for script execution.
This topic shows an example of a template that deploys an application to a test environment and assigns testing to QA. When testing succeeds, Release sends an email notification. If the testing fails, it tries again with the next version of the application.
When creating release templates, you will create tasks that contain information that varies based on the release. For example, you can have one generic release template that is used for the release process of several applications. Different releases based on this template will require different application names.