🧭 Digital.ai Release (XL Release) – Complete Terminology & Definitions

1. Release

A release is the central entity in XL Release — representing a deployment or delivery process (e.g., a software release, change rollout, or CI/CD pipeline).
It is made up of phases, tasks, and dependencies, and tracks progress from start to finish.

2. Template

A template defines the reusable structure of a release — including phases, tasks, gates, and variables.
Templates can be cloned to create actual releases with pre-defined configurations and workflows.

3. Phase

A phase is a logical grouping of tasks in a release (e.g., “Build”, “Test”, “Deploy”, “Verify”).
Phases help organize complex release workflows into manageable sections.

4. Task

A task is an individual step in a phase.
Tasks can be:

• Manual Tasks – require human input or approval.
• Automated Tasks – executed automatically using integrations (e.g., Jenkins, Ansible, Jira, etc.).
• Script Tasks – run custom scripts (Python, Shell, PowerShell, Groovy, etc.).

5. Gate

A gate is a checkpoint or approval step between phases.
It ensures compliance or verification before progressing to the next phase.
For example, a “QA Approval” gate before the “Deploy to Production” phase.

6. Variable

A variable stores data used across a release or template — such as credentials, environment names, or version numbers.
Variables can be:

• Global (available across all releases)
• Template-level
• Release-level
• Task-level

They can also be masked (secure) for sensitive data like passwords or tokens.

7. Trigger

A trigger automatically starts a release or task when certain conditions are met.
Examples:

• A new artifact in Jenkins
• A webhook from GitHub
• A scheduled time (cron-based)

8. Release Flow / Pipeline

A release flow defines the end-to-end orchestration of phases and tasks that move software from development to production.
It can include parallel paths, conditions, and approvals.

9. Dependency

A dependency specifies that one release or task depends on another.
This helps control order and timing — e.g., “Release B can start only after Release A finishes successfully.”

10. Environment

An environment represents the target infrastructure where deployments or tests happen — like Dev, QA, UAT, or Prod.
Environments can have associated configurations and permissions.

11. Team

A team defines users and their roles for specific releases or templates.
Each team can have different permissions — such as Release Admin, Release Engineer, Viewer, etc.

12. Role

A role defines access control privileges in XL Release.
For example:

• Release Admin – full control
• Template Owner – can edit templates
• Viewer – read-only access
• Task Assignee – can execute assigned tasks

13. Folder

A folder is a logical grouping of releases, templates, and teams.
It’s used to organize projects or departments (e.g., “Payments”, “Infrastructure”, “HR”).

14. Permissions

Permissions define who can view, create, edit, or execute releases, templates, or tasks.
They are managed at the folder or team level.

15. Release Dashboard

A dashboard provides real-time visualization of all releases — showing progress, bottlenecks, overdue tasks, and metrics.

16. Reports

Reports summarize release performance, audit trails, task completion rates, and SLA metrics.
They support compliance and management reporting.

17. Audit Trail

Every change, execution, or approval in a release is logged in an immutable audit trail for compliance and traceability.

18. External Task / Integration

These are automated tasks that integrate with external tools such as:

• Jenkins (CI pipelines)
• Ansible (infrastructure automation)
• ServiceNow / Jira (change management)
• Git / GitHub / GitLab
• XL Deploy / Digital.ai Deploy

19. Script Task

A script task runs custom code inside XL Release to perform dynamic logic — often written in Python, Groovy, or PowerShell.
Useful for integrating APIs or conditional execution.

20. Condition Task

A condition task checks a boolean condition (true/false) to control flow — often used to skip or continue phases dynamically.

21. Parallel Task Group

A parallel group allows multiple tasks to execute simultaneously within a phase — ideal for speeding up workflows.

22. Checkpoint

A checkpoint marks an important milestone or progress marker in a release — similar to a bookmark.

23. Task Assignee

The assignee is the user or team responsible for completing a task.
For manual tasks, the assignee must explicitly mark it “done”.

24. Comments / Notes

Users can add comments or notes on tasks, phases, or releases to provide context or documentation.

25. Flag / Marker

A flag is a visual indicator (like a warning or alert) marking attention-required tasks (e.g., failed automation, overdue task).

26. Release ID / Key

Each release has a unique identifier (e.g., RLS-1234) used for tracking, integration, and reporting.

27. Release State

Releases can be in states like:

• Planned – not started yet
• In Progress – executing
• Paused – temporarily stopped
• Completed – finished successfully
• Aborted / Failed – terminated or failed

28. Scheduled Release

A release scheduled to start automatically at a specific time/date — helpful for maintenance windows or nightly deployments.

29. Variables Panel

UI area in XL Release to view and override variables for a specific release instance before starting it.

30. REST API / Webhooks

XL Release exposes REST APIs and webhooks to:

• Create or trigger releases
• Update tasks
• Fetch release data programmatically
  Used widely for DevOps toolchain integrations.

31. Plugins / Extensions

Reusable integrations that extend XL Release functionality (e.g., Slack notifications, ServiceNow approvals, AWS automation).

32. SLA / KPI Metrics

Metrics to measure release performance and compliance — e.g.:

• Lead time
• Mean time to deploy (MTTD)
• Approval delays
• Task completion times

33. Release Calendar

A visual timeline showing all scheduled releases and environments, helping prevent deployment overlaps or conflicts.

34. Governance / Compliance

Policies and audit checks that ensure releases follow organization’s standards and regulatory compliance.

35. Digital.ai Platform

XL Release is part of the Digital.ai DevOps Platform, integrated with:

• Digital.ai Deploy (XL Deploy)
• Digital.ai Agility (VersionOne)
• Digital.ai Intelligence (Analytics)

36. Blueprints

Pre-built release templates or best practice patterns for common scenarios (e.g., CI/CD pipeline, multi-environment deployment).

37. Task Execution Logs

Detailed logs of each task execution, stored in XL Release for debugging and traceability.

38. Failure Strategy

Defines what happens when a task fails:

• Stop the release
• Continue to next task
• Manual intervention required

39. Notifications

XL Release can send email or chat notifications on key events (task completion, failure, approvals, etc.).

40. Role-Based Access Control (RBAC)

Security mechanism defining who can access what in the system, using roles and team assignments.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.