64 docs tagged with "release"

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.

By default, when a task in a release fails, the release stops so you can retry the task, skip the task, or add new tasks to resolve the issue. If the Abort on failure option is selected, the release immediately aborts if a failure occurs. This is useful for Continuous Integration/Continuous Delivery environments in which a new code commit will fix the problem and start a new release.

To see an overview of all releases in Digital.ai Release, from the navigation pane, select Release Calendar under the Overview group.

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.

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.

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.

A Create Delivery task is an automatic task that creates a new delivery from a delivery pattern.

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.

In Digital.ai Release you can use dashboard templates to quickly build a dashboard that provides information on your deployments and releases.

Digital.ai Release reports show graphs and statistics based on historical release data. This data is in the archive database. Releases that are completed or aborted but not yet archived do not appear in reports.

In a large software development environment, it is common for multiple teams to be working with different tools and processes, at their own speed, on different features; but these features all need to be delivered together as part of a single monthly or quarterly feature release. At the same time, the pipelines that drive individual applications to production need synchronization at particular points such as end-to-end testing and approvals; and all applications must be present before the test can start.

A Find Delivery task is an automatic task that searches for an existing delivery by tracked item or by name.

A Find Or Create Delivery task is an automatic task that searches for an existing delivery or creates a new one from a delivery pattern.

Activity logs

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:

This section describes how to install the Release application on various Kubernetes platforms.

This section provides an introduction to Kubernetes Operator as a custom installer to deploy Digital.ai Release.

The Delivery Patterns feature in Release allows you to use deliveries and tracked items to synchronize multiple releases together. This allows you to design delivery patterns that conform to the release standards being used by your organization, such as SAFe.

The Delivery Patterns feature in Release allows you to use deliveries and tracked items to synchronize multiple releases together. This allows you to design delivery patterns that conform to the release standards being used by your organization, such as SAFe.

Keycloak is the the default authentication manager for Release. This topic describes the steps involved in configuring Keycloak before and after the Release installation.

This tutorial is intended to help you get started with DevOps as Code in Release. It describes how to generate a DevOps as Code YAML file from an existing Release template and manage it in source control.

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 to create and manage delivery patterns. A delivery pattern allows you to design a flow of stages that the tracked items in a delivery must go through. You can reuse these patterns in multiple deliveries.

A Mark Tracked Items task is an automatic task that completes or skips one or more tracked items on a running delivery.

If you want to track a new feature as part of your end to end delivery of a release, you can add the feature as a tracked item in the delivery.

A Register Tracked Items task is an automatic task that registers one or more tracked items to a running delivery.

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.

The audit report delivers full traceability and auditability to auditors. You can generate an audit report for releases that are:

In Digital.ai Release, the release dashboard tiles topic provides you with an overview of your planning information with the help of graphical representations. The release dashboard can be customized as per your requirement by adding, configuring, moving, and removing tiles to show the planning information and details about the release status.

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.

During a complete life cycle, a release passes through multiple stages.

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).

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 release value stream report focuses on the quality of completed and aborted releases. The data for this report comes from Release's archive database. Releases that are completed or aborted but not yet archived do not appear in reports.

The Release release value stream report focuses on the quality of completed and aborted releases. The data for this report comes from the Release archive database. Releases that are completed or aborted but not yet archived do not appear in reports.

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:

Release reports show graphs and statistics based on historical release data. In Release this data is stored in the archive database.

The Release reports dashboard provides important information such as releases that have been flagged and which releases have the highest level of automation. The data for this report comes from the Release archive database. Releases that are completed but not yet archived do not appear in reports.

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.

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.

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.

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

To start a release from an archived release:

Triggers allow you to set the conditions for an event to create an action, such as a release task. They can be created in the Triggers management page, or from the release template show drop-down menu.

This section describes how to troubleshoot some of the common issues you may face when installing the Release application using Operator-based installer.

You may want to uninstall the Release Operator to troubleshoot an issue where the Release installation is not working properly, or you no longer want to use the Operator. This section describes the steps to uninstall the Digital.ai Release Operator.

This section describes how to upgrade to the latest Kubernetes Operator-based Release solution on various Kubernetes platforms. Release 22.1 supports the following upgrades on the supported Kubernetes platforms:

This topic describes how to create and manage deliveries.

Note: This feature is being released in beta. There will be some changes in the next major Release version which are likely to break your YAML templates, so you should plan accordingly.

The release dashboard is a customizable view where you can add, configure, move, and remove tiles that show planning information and details about release status.

The Release support accelerator gathers data that helps the Digital.ai Support Team to troubleshoot issues.

For data that may change or that is not known in advance, Release provides a placeholder mechanism called variables.

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.

A Wait For Stage task is an automatic task that makes the running release wait for a stage to be completed on a running delivery before proceeding.

A Wait For Tracked Items task is an automatic task that waits for items to exist or be completed in a stage on a running delivery.

In Release, phases in a template or release represent blocks of activities that occur in succession. Activities in a template or release are modeled as tasks, which are logically grouped in phases. You can use the release flow editor to manage phases and tasks.