Version: Release 24.3

Glossary of Release Terms

This page defines the terms you will encounter in Digital.ai Release.

Activity logs: The activity log in a release records all events that occur during the release lifecycle, including task completions, status changes, comments, and user assignments. Each entry includes the acting user and a timestamp.
Application: An application represents a software service or component that is built and deployed by a team. Applications are tracked through their deployment lifecycle across one or more environments in Digital.ai Release.
Archive database: Completed releases are moved to a separate archive database when they are archived. Archived releases remain searchable and are retained for reporting purposes.
Blackout period: A blackout period is a configured time window during which specified tasks or deployments are blocked. Use blackout periods to enforce change freezes or restrict deployments to specific time slots.
Blueprints: Blueprints are reusable YAML structures used in DevOps as Code to define infrastructure provisioning and application deployment processes. They are applied using the XL CLI to provision environments or deploy applications consistently.
Canary release: A canary release is a deployment pattern that rolls out new code or features to a small subset of production users before a full deployment. It reduces risk by limiting initial exposure to the new version.
Cluster: A Release cluster is a group of Release server nodes that share state and operate together as a single system. Plugin installations are synchronized automatically across all nodes.
Connection: A connection stores the credentials and endpoint configuration that Digital.ai Release uses to communicate with an external system, such as Jenkins, Jira, or ServiceNow. Connections are scoped to global or folder level and are inherited by templates and releases through the folder hierarchy.
Container-based plugin: A container-based plugin is a Release plugin whose tasks run in isolated containers managed by a Release Runner, rather than inside the Release server process. Container-based plugin tasks can be written in Python or Go, as well as Jython.
Create Release task: A Create Release task is an automated task type that creates and optionally starts a new release based on a specified template. It supports dynamic template selection and variable population at runtime.
Cron pattern: A cron pattern is an expression that defines a recurring schedule. Digital.ai Release uses cron patterns with six fields representing second, minute, hour, day, month, and weekday.
Custom dashboards: Custom dashboards are user-defined views that display release status and metrics using configurable tiles. Each tile shows a specific type of data, such as task counts, release timelines, or integration status.
Custom tasks: Custom tasks are task types contributed by plugins to integrate Release with third-party tools. They appear alongside built-in task types in the release flow editor and support the same configuration and automation capabilities.
Custom tiles: Custom tiles are configurable dashboard components that display specific release data or integration output. Teams add custom tiles to dashboards to tailor their reporting view.
Dashboard: A dashboard is a configurable view that displays release status, metrics, and integration data using tiles. Digital.ai Release provides a home page dashboard, custom dashboards, and a reports dashboard.
Delivery: A delivery coordinates multiple releases into a release train, tracking items (features, fixes, or components) as they move through each contributing release. See also: Release train, Delivery patterns, Tracked item.
Delivery patterns: A delivery pattern is the repeatable structure used to assemble a delivery. It defines the stages that tracked items move through and the transitions between those stages.
DevOps as Code: DevOps as Code is an approach that defines Release objects (templates, releases, folders, variables, and connections) as YAML files. These files are provisioned using the XL CLI, enabling version control and automated configuration of Release.
Environment: An environment is a deployment target, such as Development, Staging, or Production, where applications are deployed and tracked. Linking an environment to an application lets Release show where each application is currently deployed and enforce deployment controls.
Environment availability: Environment availability is a deployment control that restricts when and what can be deployed to a specific environment. Release checks environment reservations at task execution time and blocks tasks that conflict with existing reservations.
Export Hook: An export hook is a Jython script that Digital.ai Release runs for every release that is about to be archived. Export hooks can be used to write release data to an external database for long-term reporting.
Failed task: A failed task is a task that did not complete successfully. When a task fails, Release notifies the release owner and pauses the release flow until the task is retried, skipped, or manually resolved.
Failure handler: A failure handler is a Jython script configured on a task that runs when the task fails. It can perform cleanup actions and programmatically retry, skip, or abort the task.
Folder: A folder is a hierarchical container that organizes templates, releases, workflows, and dashboards. Permissions, connections, and variables defined on a folder are inherited by all items within it and its subfolders.
Folder variables: Folder variables are variables available to all templates and releases within a specific folder and its subfolders. They are defined at the folder level.
Gantt chart: The Gantt chart in Digital.ai Release shows the planned and actual timeline of phases and tasks within a release. It is used to track schedule status and the relationships between activities.
Gate tasks: A gate task is a task type that blocks a release from proceeding until defined conditions are met. Conditions include checkboxes, approvals, or dependencies on milestones in other releases.
Git triggers: A Git trigger polls a Git repository at a defined interval and starts a release when it detects a new commit matching the configured criteria.
GitOps folder versioning: GitOps folder versioning links a Release folder to a Git repository, placing templates and folder configuration under version control. Changes are reviewed as pull requests, and the Git history provides an audit trail of all modifications.
Global variables: Global variables are variables available to all templates and releases in the Release system. They are defined by administrators and are accessible regardless of folder or release context.
Keycloak: Keycloak is an open-source identity and access management solution. Digital.ai Release supports Keycloak as an OpenID Connect (OIDC) provider for single sign-on authentication.
Kubernetes Operator: The Kubernetes Operator is used to deploy Digital.ai Release on Kubernetes platforms such as Amazon EKS, Azure AKS, and OpenShift. It manages the lifecycle of Release server components on the cluster. See Kubernetes Operator.
LDAP repository: LDAP (Lightweight Directory Access Protocol) is an open, cross-platform protocol for directory services authentication. Digital.ai Release can authenticate users against an LDAP directory such as Microsoft Active Directory.
Live Deployments: The Live Deployments page shows the current deployment state of all applications across all environments in real time, including hybrid and multi-cloud targets.
Load balancer: In a Release cluster, a load balancer distributes incoming HTTP traffic across Release server nodes. It provides a single entry point for users and external systems while improving availability and throughput.
Machine learning: Digital.ai Release uses machine learning on historical release data to estimate task duration and predict failure risk before a release starts. These predictions are surfaced through the risk-aware view.
Maintenance window: A maintenance window is a pre-scheduled time period designated for planned maintenance on software or infrastructure. In Release, maintenance windows can be configured to control when specific tasks or deployments are permitted.
MCP Server: The Release MCP Server is a beta feature that provides a Model Context Protocol (MCP) interface for AI agents. It allows AI-driven tools to manage releases, templates, tasks, and variables programmatically.
Network Time Protocol (NTP) synchronization: NTP synchronization keeps clock times aligned across nodes in a Release cluster. Accurate time synchronization is required for correct scheduling, trigger timing, and audit log timestamps.
Nexus triggers: A Nexus trigger monitors a Sonatype Nexus repository for new artifact versions. When a version matching the configured criteria is published, the trigger starts a release automatically.
Notification task: A notification task is an automated task type that sends an email to configured recipients. The task completes when the message is delivered successfully.
Parallel group: A parallel group is a task container that executes multiple child tasks simultaneously within a phase. The parallel group completes when all child tasks have finished.
Personal access token: A personal access token (PAT) is a credential used for machine-to-machine authentication with Digital.ai Release. PATs are used to register Release Runners, call the REST API from scripts, and integrate external tools without user credentials.
Phase: A phase is a sequential stage within a release, such as Development, QA, or Deployment. Phases must be completed in order. Each phase contains one or more tasks that represent the work to be done in that stage.
Pipeline Orchestrator: Digital.ai Release acts as a pipeline orchestrator by automating and coordinating the steps required to deliver software to production. It tracks release progress and integration status across teams and tools.
Precondition: A precondition is a Jython expression configured on a task that determines whether the task should execute. If the expression evaluates to false, Release skips the task automatically.
Quorum: In a Release cluster, a quorum is the minimum number of active nodes required to perform certain distributed operations. Quorum prevents conflicting state updates when network partitions occur.
Release: A release is a time-boxed set of activities carried out to deliver software. Each release has a start date, an end date, an owner, and a flow of phases and tasks. Releases move through a lifecycle: planned, active, and completed (or aborted).
Release Archiving: Release archiving moves completed releases from the active database to a separate archive database. Archived releases remain searchable and can be queried for reporting. See Release Archiving.
Release Flow: The release flow is the ordered sequence of phases and tasks that the Release engine executes. When a release starts, Release activates each task in sequence: executing automated tasks directly and sending notifications for manual tasks.
Release flow editor: The release flow editor is the graphical interface for viewing and editing the phases and tasks in a release or template. You can use it to add, move, edit, and delete phases and tasks.
Release overview: The release overview shows the list of releases you have permission to view, filtered by status (planned, active, or completed). It provides a centralized view of all releases in the system.
Release Owner: The release owner is the user responsible for a release. The release owner receives notifications when a task fails, when a task is overdue, or when a team member flags an issue.
Release permission: Release permissions control what users and teams can do within a folder, template, or release. Permissions are assigned to teams and cover actions such as starting releases, editing templates, and configuring connections.
Release plugins: Release plugins are add-ons that extend Digital.ai Release with integrations for third-party tools. Plugins contribute custom task types, triggers, and dashboard tiles. Plugins run either inside the Release server process (JVM-based) or in isolated containers via a Release Runner (container-based).
Release Runner: A Release Runner is a standalone containerized process that executes container-based plugin tasks on behalf of the Release server. Runners can be deployed on Kubernetes or Docker, close to the infrastructure they target, and scale independently of the Release server.
Release train: A release train is a coordinated set of multiple releases managed through a delivery. Each release in the train contributes to tracking items (features, fixes, or components) as they move toward completion.
Release value stream: The release value stream report shows where delays and failures occur across completed and aborted releases. It helps teams identify bottlenecks in the release process.
Release variables: Release variables are variables scoped to a specific template or release. They act as named placeholders for values supplied at release creation time or updated during the release.
Risk profile: A risk profile is a configuration that defines the factors used to calculate a release risk score, including task failure rates, overdue items, and missing assignees. Risk profiles are assigned to templates and applied to all releases created from them.
Role: A role defines the level of access granted to users and teams within Digital.ai Release. Roles are defined at the global level and assigned to teams on folders, templates, and releases. Permissions are granted to teams based on their assigned role.
Runner capabilities: Runner capabilities are labels assigned to a Release Runner that determine which container-based tasks it can execute. A task declares the capability labels it requires, and Release routes the task only to Runners with matching labels.
Scheduled script: A scheduled script is a Jython script used within a custom task that polls an external system at a defined interval. The script checks for a condition (such as a build completing) and signals the task to complete when the condition is met.
Script task: A script task is an automated task type that executes a Jython or Groovy script. Script tasks are used for custom logic, integrations, and automation steps that are not covered by plugin task types.
Sequential group: A sequential group is a task container that executes child tasks in a defined order. Each child task starts only after the previous one completes.
SVN triggers: An SVN trigger polls a Subversion repository at a defined interval and starts a release when it detects a new commit matching the configured criteria.
System message: A system message is an admin-configured banner displayed to all users on the Digital.ai Release interface. Administrators use system messages to communicate planned maintenance, system status updates, or other notices to all logged-in users.
Task: A task is an individual unit of work within a release phase. Tasks are either manual (requiring a person to act) or automated (executed by the Release engine). Built-in task types include gate tasks, script tasks, notification tasks, user input tasks, parallel groups, and sequential groups.
Team: A team is a group of users assigned a role within a folder, template, or release. Permissions are granted to teams, and teams determine who can act on specific tasks and receive notifications. Teams are defined primarily at the folder level, where they apply to all templates and releases within that folder.
Template: A template is a reusable blueprint from which releases are created. It defines the phase and task structure, team assignments, and variables. Templates are never executed directly; they are used to start releases.
Tracked item: A tracked item is a feature, fix, or component registered in a delivery that is monitored as it moves through delivery stages. Each tracked item has a status that reflects its progress through the contributing releases.
Triggers: Triggers start releases automatically in response to external events or schedules. Digital.ai Release supports Git triggers, SVN triggers, Nexus triggers, webhooks, and Cron triggers.
User Input task: A user input task is a manual task type that prompts a user for information. The user's responses are stored as release variables and are available to subsequent tasks in the release flow.
Variable: A variable is a named placeholder that stores a value in a template or release. Variables use the $ syntax and support types including text, password, number, and list. Variables can be scoped to a release, a folder, or the entire system.
Webhooks: A webhook allows an external system to start a release in Digital.ai Release by sending an HTTP request to a configured endpoint. The webhook payload can populate release variables.
Work directory: The work directory is a temporary file storage location used by Release tasks during execution. Files that cannot be held in memory, such as those created during configuration item (CI) creation, are written to the work directory.
Workflow: A self-service workflow is a step-by-step guided process for a single user to complete a utility task, such as onboarding an application, provisioning a cloud resource, or rotating a secret. Unlike releases, which coordinate work across multiple people, a workflow is designed for one user and typically completes in minutes.