{"id":54018,"date":"2025-11-04T22:38:39","date_gmt":"2025-11-04T22:38:39","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=54018"},"modified":"2025-11-04T22:38:39","modified_gmt":"2025-11-04T22:38:39","slug":"xl-release-digital-ai-release-terminology","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/xl-release-digital-ai-release-terminology\/","title":{"rendered":"XL Release – Digital.ai release Terminology"},"content":{"rendered":"\n

<\/p>\n\n\n\n

\n\n\n\n

\ud83e\udded Digital.ai Release (XL Release) \u2013 Complete Terminology & Definitions<\/strong><\/h1>\n\n\n\n

1. Release<\/strong><\/h3>\n\n\n\n

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

\n\n\n\n

2. Template<\/strong><\/h3>\n\n\n\n

A template<\/strong> defines the reusable structure<\/strong> of a release \u2014 including phases, tasks, gates, and variables.
Templates can be cloned to create actual releases with pre-defined configurations and workflows.<\/p>\n\n\n\n

\n\n\n\n

3. Phase<\/strong><\/h3>\n\n\n\n

A phase<\/strong> is a logical grouping of tasks<\/strong> in a release (e.g., \u201cBuild\u201d, \u201cTest\u201d, \u201cDeploy\u201d, \u201cVerify\u201d).
Phases help organize complex release workflows into manageable sections.<\/p>\n\n\n\n

\n\n\n\n

4. Task<\/strong><\/h3>\n\n\n\n

A task<\/strong> is an individual step<\/strong> in a phase.
Tasks can be:<\/p>\n\n\n\n

    \n
  • Manual Tasks<\/strong> \u2013 require human input or approval.<\/li>\n\n\n\n
  • Automated Tasks<\/strong> \u2013 executed automatically using integrations (e.g., Jenkins, Ansible, Jira, etc.).<\/li>\n\n\n\n
  • Script Tasks<\/strong> \u2013 run custom scripts (Python, Shell, PowerShell, Groovy, etc.).<\/li>\n<\/ul>\n\n\n\n
    \n\n\n\n

    5. Gate<\/strong><\/h3>\n\n\n\n

    A gate<\/strong> is a checkpoint or approval step<\/strong> between phases.
    It ensures compliance or verification before progressing to the next phase.
    For example, a \u201cQA Approval\u201d gate before the \u201cDeploy to Production\u201d phase.<\/p>\n\n\n\n

    \n\n\n\n

    6. Variable<\/strong><\/h3>\n\n\n\n

    A variable<\/strong> stores data used across a release or template \u2014 such as credentials, environment names, or version numbers.
    Variables can be:<\/p>\n\n\n\n

      \n
    • Global<\/strong> (available across all releases)<\/li>\n\n\n\n
    • Template-level<\/strong><\/li>\n\n\n\n
    • Release-level<\/strong><\/li>\n\n\n\n
    • Task-level<\/strong><\/li>\n<\/ul>\n\n\n\n

      They can also be masked (secure)<\/strong> for sensitive data like passwords or tokens.<\/p>\n\n\n\n

      \n\n\n\n

      7. Trigger<\/strong><\/h3>\n\n\n\n

      A trigger<\/strong> automatically starts a release or task<\/strong> when certain conditions are met.
      Examples:<\/p>\n\n\n\n

        \n
      • A new artifact in Jenkins<\/li>\n\n\n\n
      • A webhook from GitHub<\/li>\n\n\n\n
      • A scheduled time (cron-based)<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n

        8. Release Flow \/ Pipeline<\/strong><\/h3>\n\n\n\n

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

        \n\n\n\n

        9. Dependency<\/strong><\/h3>\n\n\n\n

        A dependency<\/strong> specifies that one release or task depends on another.
        This helps control order and timing \u2014 e.g., \u201cRelease B can start only after Release A finishes successfully.\u201d<\/p>\n\n\n\n

        \n\n\n\n

        10. Environment<\/strong><\/h3>\n\n\n\n

        An environment<\/strong> represents the target infrastructure<\/strong> where deployments or tests happen \u2014 like Dev<\/em>, QA<\/em>, UAT<\/em>, or Prod<\/em>.
        Environments can have associated configurations and permissions.<\/p>\n\n\n\n

        \n\n\n\n

        11. Team<\/strong><\/h3>\n\n\n\n

        A team<\/strong> defines users and their roles<\/strong> for specific releases or templates.
        Each team can have different permissions \u2014 such as Release Admin<\/em>, Release Engineer<\/em>, Viewer<\/em>, etc.<\/p>\n\n\n\n

        \n\n\n\n

        12. Role<\/strong><\/h3>\n\n\n\n

        A role<\/strong> defines access control privileges<\/strong> in XL Release.
        For example:<\/p>\n\n\n\n

          \n
        • Release Admin<\/em> \u2013 full control<\/li>\n\n\n\n
        • Template Owner<\/em> \u2013 can edit templates<\/li>\n\n\n\n
        • Viewer<\/em> \u2013 read-only access<\/li>\n\n\n\n
        • Task Assignee<\/em> \u2013 can execute assigned tasks<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n

          13. Folder<\/strong><\/h3>\n\n\n\n

          A folder<\/strong> is a logical grouping of releases, templates, and teams<\/strong>.
          It\u2019s used to organize projects or departments (e.g., \u201cPayments\u201d, \u201cInfrastructure\u201d, \u201cHR\u201d).<\/p>\n\n\n\n

          \n\n\n\n

          14. Permissions<\/strong><\/h3>\n\n\n\n

          Permissions<\/strong> define who can view, create, edit, or execute<\/strong> releases, templates, or tasks.
          They are managed at the folder or team level.<\/p>\n\n\n\n

          \n\n\n\n

          15. Release Dashboard<\/strong><\/h3>\n\n\n\n

          A dashboard<\/strong> provides real-time visualization<\/strong> of all releases \u2014 showing progress, bottlenecks, overdue tasks, and metrics.<\/p>\n\n\n\n

          \n\n\n\n

          16. Reports<\/strong><\/h3>\n\n\n\n

          Reports<\/strong> summarize release performance, audit trails, task completion rates, and SLA metrics.
          They support compliance and management reporting.<\/p>\n\n\n\n

          \n\n\n\n

          17. Audit Trail<\/strong><\/h3>\n\n\n\n

          Every change, execution, or approval in a release is logged in an immutable audit trail<\/strong> for compliance and traceability.<\/p>\n\n\n\n

          \n\n\n\n

          18. External Task \/ Integration<\/strong><\/h3>\n\n\n\n

          These are automated tasks<\/strong> that integrate with external tools such as:<\/p>\n\n\n\n

            \n
          • Jenkins<\/strong> (CI pipelines)<\/li>\n\n\n\n
          • Ansible<\/strong> (infrastructure automation)<\/li>\n\n\n\n
          • ServiceNow \/ Jira<\/strong> (change management)<\/li>\n\n\n\n
          • Git \/ GitHub \/ GitLab<\/strong><\/li>\n\n\n\n
          • XL Deploy \/ Digital.ai Deploy<\/strong><\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n

            19. Script Task<\/strong><\/h3>\n\n\n\n

            A script task<\/strong> runs custom code<\/strong> inside XL Release to perform dynamic logic \u2014 often written in Python, Groovy, or PowerShell.
            Useful for integrating APIs or conditional execution.<\/p>\n\n\n\n

            \n\n\n\n

            20. Condition Task<\/strong><\/h3>\n\n\n\n

            A condition task<\/strong> checks a boolean condition<\/strong> (true\/false) to control flow \u2014 often used to skip or continue phases dynamically.<\/p>\n\n\n\n

            \n\n\n\n

            21. Parallel Task Group<\/strong><\/h3>\n\n\n\n

            A parallel group<\/strong> allows multiple tasks to execute simultaneously<\/strong> within a phase \u2014 ideal for speeding up workflows.<\/p>\n\n\n\n

            \n\n\n\n

            22. Checkpoint<\/strong><\/h3>\n\n\n\n

            A checkpoint<\/strong> marks an important milestone or progress marker in a release \u2014 similar to a bookmark.<\/p>\n\n\n\n

            \n\n\n\n

            23. Task Assignee<\/strong><\/h3>\n\n\n\n

            The assignee<\/strong> is the user or team responsible for completing a task.
            For manual tasks, the assignee must explicitly mark it \u201cdone\u201d.<\/p>\n\n\n\n

            \n\n\n\n

            24. Comments \/ Notes<\/strong><\/h3>\n\n\n\n

            Users can add comments or notes<\/strong> on tasks, phases, or releases to provide context or documentation.<\/p>\n\n\n\n

            \n\n\n\n

            25. Flag \/ Marker<\/strong><\/h3>\n\n\n\n

            A flag<\/strong> is a visual indicator (like a warning or alert) marking attention-required tasks (e.g., failed automation, overdue task).<\/p>\n\n\n\n

            \n\n\n\n

            26. Release ID \/ Key<\/strong><\/h3>\n\n\n\n

            Each release has a unique identifier<\/strong> (e.g., RLS-1234<\/code>) used for tracking, integration, and reporting.<\/p>\n\n\n\n

            \n\n\n\n

            27. Release State<\/strong><\/h3>\n\n\n\n

            Releases can be in states like:<\/p>\n\n\n\n

              \n
            • Planned<\/strong> \u2013 not started yet<\/li>\n\n\n\n
            • In Progress<\/strong> \u2013 executing<\/li>\n\n\n\n
            • Paused<\/strong> \u2013 temporarily stopped<\/li>\n\n\n\n
            • Completed<\/strong> \u2013 finished successfully<\/li>\n\n\n\n
            • Aborted \/ Failed<\/strong> \u2013 terminated or failed<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              28. Scheduled Release<\/strong><\/h3>\n\n\n\n

              A release scheduled<\/strong> to start automatically at a specific time\/date \u2014 helpful for maintenance windows or nightly deployments.<\/p>\n\n\n\n

              \n\n\n\n

              29. Variables Panel<\/strong><\/h3>\n\n\n\n

              UI area in XL Release to view and override variables<\/strong> for a specific release instance before starting it.<\/p>\n\n\n\n

              \n\n\n\n

              30. REST API \/ Webhooks<\/strong><\/h3>\n\n\n\n

              XL Release exposes REST APIs<\/strong> and webhooks<\/strong> to:<\/p>\n\n\n\n

                \n
              • Create or trigger releases<\/li>\n\n\n\n
              • Update tasks<\/li>\n\n\n\n
              • Fetch release data programmatically
                Used widely for DevOps toolchain integrations.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n\n

                31. Plugins \/ Extensions<\/strong><\/h3>\n\n\n\n

                Reusable integrations that extend XL Release functionality<\/strong> (e.g., Slack notifications, ServiceNow approvals, AWS automation).<\/p>\n\n\n\n

                \n\n\n\n

                32. SLA \/ KPI Metrics<\/strong><\/h3>\n\n\n\n

                Metrics to measure release performance and compliance<\/strong> \u2014 e.g.:<\/p>\n\n\n\n

                  \n
                • Lead time<\/li>\n\n\n\n
                • Mean time to deploy (MTTD)<\/li>\n\n\n\n
                • Approval delays<\/li>\n\n\n\n
                • Task completion times<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  33. Release Calendar<\/strong><\/h3>\n\n\n\n

                  A visual timeline showing all scheduled releases and environments<\/strong>, helping prevent deployment overlaps or conflicts.<\/p>\n\n\n\n

                  \n\n\n\n

                  34. Governance \/ Compliance<\/strong><\/h3>\n\n\n\n

                  Policies and audit checks that ensure releases follow organization\u2019s standards<\/strong> and regulatory compliance<\/strong>.<\/p>\n\n\n\n

                  \n\n\n\n

                  35. Digital.ai Platform<\/strong><\/h3>\n\n\n\n

                  XL Release is part of the Digital.ai DevOps Platform<\/strong>, integrated with:<\/p>\n\n\n\n

                    \n
                  • Digital.ai Deploy (XL Deploy)<\/strong><\/li>\n\n\n\n
                  • Digital.ai Agility (VersionOne)<\/strong><\/li>\n\n\n\n
                  • Digital.ai Intelligence (Analytics)<\/strong><\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n

                    36. Blueprints<\/strong><\/h3>\n\n\n\n

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

                    \n\n\n\n

                    37. Task Execution Logs<\/strong><\/h3>\n\n\n\n

                    Detailed logs of each task execution, stored in XL Release for debugging and traceability.<\/p>\n\n\n\n

                    \n\n\n\n

                    38. Failure Strategy<\/strong><\/h3>\n\n\n\n

                    Defines what happens when a task fails:<\/p>\n\n\n\n

                      \n
                    • Stop the release<\/strong><\/li>\n\n\n\n
                    • Continue to next task<\/strong><\/li>\n\n\n\n
                    • Manual intervention required<\/strong><\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n

                      39. Notifications<\/strong><\/h3>\n\n\n\n

                      XL Release can send email or chat notifications<\/strong> on key events (task completion, failure, approvals, etc.).<\/p>\n\n\n\n

                      \n\n\n\n

                      40. Role-Based Access Control (RBAC)<\/strong><\/h3>\n\n\n\n

                      Security mechanism defining who can access what<\/strong> in the system, using roles and team assignments.<\/p>\n\n\n\n

                      \n\n\n\n

                      <\/p>\n","protected":false},"excerpt":{"rendered":"

                      \ud83e\udded Digital.ai Release (XL Release) \u2013 Complete Terminology & Definitions 1. Release A release is the central entity in XL Release \u2014 representing a deployment or delivery process (e.g., a… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-54018","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54018","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=54018"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54018\/revisions"}],"predecessor-version":[{"id":54019,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54018\/revisions\/54019"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=54018"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=54018"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=54018"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}