๐๏ธ Release Overview
The release overview shows the list of releases that you have permission to view and that are planned, active (including releases that are in progress, paused, failing, or failed), or completed (including aborted).
๐๏ธ Release Lifecycle
During a complete life cycle, a release passes through multiple stages.
๐๏ธ Configure Release Properties
To specify metadata for a release or template, select Properties from the Show menu to go to the release properties page.
๐๏ธ Release Views
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:
๐๏ธ Risk Awareness
Release calculates a risk level for each release based on different factors such as flags, failed or failing states, or due dates. You can see the releases with a high risk level and take the appropriate actions.
๐๏ธ Release Flow Editor
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.
๐๏ธ Release Table View
The Release table view provides an alternative view of a template or release that is optimized for working with tasks.
๐๏ธ Release Activity Logs
The activity log shows all the events that occur in a release, providing an audit trail of all the actions performed by users and the related dates and times. To open the activity log, select Activity logs from the Show menu.
๐๏ธ Create Release in Another Folder
Earlier, all the teams in Release had read-only access to all the templates but cannot execute them. This was possible because you can create releases only in the folder where the template is available.
๐๏ธ Start a Release From an Archived Release
To start a release from an archived release:
๐๏ธ Start a Release From Another Release
With the Create Release task type you can automatically create and start a release based on a configured template. You can use the Create Release task for several different release orchestration scenarios.
๐๏ธ Create a Release From a Git Repository
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.
๐๏ธ Code Releases Using the Releasefile
With Digital.ai Release you can define a release from a Groovy-based DSL script, that describes all the phases, tasks, and task-groups in the release. This enables you to store release definitions as code in version control and gives you programmatic control over a release when creating it.
๐๏ธ Load Test Data During a Release
Release can help you prepare your environments for testing through tasks that load test data in environments.
๐๏ธ Restart a Phase in an Active Release
In an active release, you can abort the current phase and restart the execution from any past phase. This can be required if some parts of the release procedure must be repeated. For example, QA rejects a version of the application for release and the test phase must be repeated with an updated version.
๐๏ธ Schedule Releases
In Release, you can schedule your releases by setting start dates and times, end dates and times, and durations on templates, releases, phases, and tasks. When you set dates and durations on phases and tasks, Release automatically adjusts other phases and calculates the release duration and end date.
๐๏ธ Calendar View
To see an overview of all releases in Digital.ai Release, from the navigation pane, select Release Calendar under the Overview group.
๐๏ธ Release Planner View
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.
๐๏ธ Set Blackout Period
Release allows you to set a start date and end date to ensure that specific tasks cannot be performed during the set blackout period.