62 docs tagged with "release"

In Release, the phases in a template or release represent blocks of work that happen in succession.

You can now add Stage Owners to Deliveries.

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 provides information about how to automatically handle failures in Release tasks.

This topic provides an overview of the calendar features in Digital.ai Release, including different views (day, week, month, year) and how to filter and export the calendar.

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 explains how Digital.ai Release 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.

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

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

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.

This topic explains how to use dashboard templates in Digital.ai Release to quickly build a dashboard that provides information on your deployments and releases.

Delivery Patterns in Release allow you to create pipelines where each team can work at its own timelines and tools, and converge at synchronized points.

Explore the preconfigured Mobile Banking demo template included with the Digital.ai Release SaaS trial. Learn how to open it, create a release, and understand each phase and task.

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.

This page defines the terms you will encounter in Release.

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.

Note: Here is a basic setup for the AWS Openshift cluster,

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.

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.

Delivery stage transitions force all the tracked items in a stage to wait together until the transition conditions are met, or the transition is manually completed. This allows you to synchronize the releases together based on criteria such as business approval, scheduling, or the status of tracked items.

This topic describes how to create, run, and manage workflows.

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.

Learn how to capture task output properties in Digital.ai Release, map them to variables, and reuse those variables in subsequent tasks for efficient pipeline management.

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

The DevOps as Code Guide is not applicable to Release SaaS. This page provides guidance and references for on-premises users.

The Installation Guide is not applicable to Release SaaS. This page provides guidance and references for on-premises users.

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.

This topic provides an overview of Digital.ai Release reports, including types of dashboards, report permissions, and report caching. Digital.ai Release reports display graphs and statistics based on historical release data stored in the archive database, and are available to users with the appropriate permissions.

This topic describes how release reports display graphs and statistics based on historical release data.

This how-to provides comprehensive guidance on configuring your user profile settings in Release, including updating personal information, changing your password, setting regional preferences, and managing product analytics and guidance options. It covers how to access and modify your profile, explains the impact of each setting, and provides step-by-step instructions to ensure your account is personalized and secure.

This topic describes how to add one or more tracked items to a 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.

This topic covers the audit report in Digital.ai Release, which provides full traceability and auditability for auditors. You can generate an audit report for releases that are in progress, completed, or archived.

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 History provides a complete audit trail of all activities performed in a release, capturing user actions along with dates and times. This helps track progress, monitor changes, and troubleshoot issues with greater visibility.

This topic explains the different stages and states a release goes through during its lifecycle in Digital.ai Release.

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.

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.

This topic provides information on the Release value stream report, which evaluates the quality of completed and aborted releases. The report draws data from the Release archive database, so it does not include releases that are completed or aborted but not yet archived. For more information, see completed and aborted and archive database.

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:

This topic provides key information on flagged releases and highlights those with the highest level of automation.

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.

This topic describes how to create a release from a template using various methods and the steps required before starting the release.

This topic explains how to start a new release from an archived release by using the original template and variable values

This topic describes how to create and manage deliveries.

Dependent properties within the XML type-definitions enables dynamic user inputs that adapt based on user selections. This functionality is essential for tasks requiring context-specific input, ensuring that only relevant fields and options are presented, thereby enhancing the user experience.

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.

Digital.ai Release uses variables to make your release templates more flexible and reusable. Variables allow you to parameterize your release processes, making it easier to manage dynamic content and configuration across different environments and scenarios.

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.

Note: Workflows are bundled with the Release application by default. However, you must have the relevant plugins installed to view these workflows in the Workflows folder. For example, you must have the Deploy plugin installed in Release to view the workflows in the Workflows > Digital.ai Deploy folder.

Only custom workflows are available for Release SaaS Trial.