Digital.ai Release 24.3.x release notes

Support Policy

See Digital.ai Support Policy.

Upgrade Instructions

The Digital.ai Release upgrade process you use depends on the version from which you are upgrading, and the version to which you want to go.

For upgrade instructions, see:

• Upgrade Release—on JVM
• Upgrade Release—on Kubernetes

Important: PostgreSQL is the recommended database for any fresh installation of Release 24.3 and later. Contact your Digital.ai representative if you prefer to use a database other than PostgreSQL for your new Release setup. For more information, see supported databases.

Breaking Changes

Here's a list of breaking changes in Release 24.3.

Activity Logs Messages

While updating the Activity Logs functionality for releases, templates, triggers, and deliveries, we have standardized the format of the activity text messages. It is not recommended to rely on the wording of these messages, as they may change in the future. Review your workflows to see if they depend on the message text and make any necessary updates.

Application Pipelines

The Application Pipelines feature has been superseded by Live Deployments. To learn more about what happens on upgrade of a site from Release 24.1 (or earlier) with Application Pipelines to Release 24.3, see Upgrade with Live Deployments.

End-of-life Notifications

Here's what is being deprecated or going out of support.

Template Versioning Updates

Release currently offers two methods for template versioning:

• Traditional template versioning
• GitOps-enabled versioning using YAML files

In our ongoing efforts to enhance Release, we have decided to prioritize the expansion of GitOps-enabled versioning using YAML files and will no longer enhance the traditional template versioning functionality.

The planned changes for Template versioning are as follows:

• Starting with the Release 24.3, template versioning and associated settings will be disabled for Release instances that do not currently utilize it. For more information, see Template Version Control.
• Existing customers with template versions stored in the database will not be impacted in any way.

The current template versioning has limitations due to its inability to read from Git repositories, which limits its usage to local server instances. This limitation blocks seamless collaboration and cross-instance sharing, thus hindering further expansion of this functionality. Therefore, we highly recommend you to consider upgrading to GitOps YAML-based versioning. This transition aligns with our commitment to security and interoperability, providing a more comprehensive and widely accepted solution for versioning and managing templates.

If you have any concerns or require further assistance, complete this survey or reach out to your Customer Success Manager or Digital.ai Support. Your feedback enables us to improve the product together.

Retiring the Task Modal

In line with our commitment to enhancing the user experience for managing tasks within Release, we are announcing a change in how tasks are handled.

The Release 24.3 is the final version that supports the Task Modal in the Release user interface. With 2025 versions, only the Task Drawer is available for creating and managing tasks. Transitioning to a single version (Task Drawer) allows for faster iterations and the introduction of new functionalities. Additionally, recent features added to the Task Drawer are incompatible with the older Task Modal.

To learn how to use the Task Drawer and explore its recent features, see:

• How to use the Task Drawer
• Recent changes in the Task Drawer

Contact the Digital.ai Customer Success Manager or Digital.ai Support should you have any questions or concerns.

Live Deployments

Digital.ai Release 24.3 brings you Live Deployments. This feature enables you to track deployments from various sources and embed them in your release process. Previously, only deployments that were started from a task in the release process were known in Release. Now you can listen to deployment events from external tools like Digital.ai Deploy and ArgoCD and view live updates in Release. Now all deployment activity is on the same page, whether it comes from cloud-native Kubernetes environments or classic middleware. Additionally, you can make the external deployments part of the release flow, even when they are not orchestrated by Release.

• The Live Deployments dashboard helps you track "what is deployed where" and "what is the status of the deployed applications".
• Digital.ai Deploy and ArgoCD are supported. Support for other tools will be available in subsequent versions.
• Embed live deployment event in your release process using Webhook Event Triggers and the Webhook: Wait for Deployment Event task.

For more information, see Live Deployments in Release.

Applications and Environments in folders

Applications and Environments are now available at the folder level. Previously, they could only be defined at the global level. What's more, they are automatically created and updated for live deployments coming from Digital.ai Deploy and ArgoCD, saving a lot of manual housekeeping. The Applications and Environments feature is used for dashboards, audit reports and resource management in the environment calendar.

For more information, see:

• Applications
• Environments

Analytics

The Release 24.3 Premium edition brings you analytics that offer deeper insights and data visualization.

The Premium edition offers a comprehensive set of analytics dashboards, each tailored to specific user roles. These include:

• DevOps Research and Assessment (DORA) Dashboard: DORA dashboard lets you analyze details to streamline or improve your DevOps process using key DORA metrics such as the deployment frequency, lead time for change, mean time to restore, and change failure rate. DORA metrics have now become the standard for gauging the efficacy of software development teams and can provide crucial insights into growth areas. For more information, see DORA Dashboards.

• Workflow Adoption and Usage Patterns Dashboard: Lets you gain insights on team adoption of services and automation via Workflows. Identify what works best and manage your developer platform as a product. For more information, see Workflow Adoption and Usage Patterns Dashboards.

• Persona-based Dashboards: These dashboards cater to specific personas such as the DevOps COE, Engineering Managers, Platform Engineers, Platform Product Managers, and Release Managers. For more information, see Overview of Analytics Dashboards.

• Custom Dashboards and Data Sets: You can create custom dashboards with the most relevant data for your team and share them with others in your organization. Custom dashboards give you the flexibility to focus on a small dataset or a specific topic such as security.

Set Up Analytics

Configuring analytics for your installation involves a few steps such as connecting your Release instance to the Digital.ai Platform, configuring the data sources, setting up roles and permissions, and so on. Contact Digital.ai Support for assistance in setting up Analytics.

For more information, see Setting up Analytics.

When Connected to Analytics

When connected to the Analytics server, you can:

• View the list of available dashboards in Release.

  

• Manage dashboards—Analytics author users can manage dashboards. Click Manage Dashboard, go to the Digital.ai Platform, create and edit dashboards, which can then be published to Digital.ai Release for all users to see. For more information, see Manage Dashboards.

  

As an Analytics user, you can:

• Use filters to sort dashboards by category or author.
• Mark specific dashboards as favorites by clicking the star icon to add them to the Favorites tab.
• When you revisit the Analytics page, it takes you to the last visited tab. For example, if you were on the Favorites tab of the Analytics page, browse away to other pages in Release, and come back to the Analytics page, it will take you directly to the Favorites tab.

Workflow Enhancements

Task Groups in Workflows

We've added support for parallel and sequential group tasks in workflow templates. Task groups help combine related activities into a single action, making the execution flow easier to visualize and more intuitive for users to follow. For example, when running multiple scripts after each other, you can use a task group to hide these scripts from the main view and show a cleaner layout. You can even parallelize tasks to improve performance.

Note: In order to keep workflow execution straightforward and clean, workflow templates only support a single level of nesting.

Improvements to Workflow Execution Pages

We've done a number of improvements on how workflows are being displayed.

First of all, there is a redesigned infopanel on the left that has all essentials information about the currently running workflow in it. It has a progress tracker, main description and shortcuts to template and design view.

The progress sidebar on the right-hand side of the screen also got a makeover to make it easier to see where you are in the process and what you need to do.

Git Scan Workflow

CheckmarxOne Scan Git Repository Workflow: Run the CheckmarxOne Scan Git Repository workflow to scan your git repository, review scan results, and verify compliance from within the Digital.ai Release interface.

Release Plugin for Backstage

Release Templates in Backstage

Fo users of Backstage, we have released a plugin to integrate with Digital.ai Release. It allows you to see an overview of running releases and available templates, right in the Backstage UI. For more information, see Overview.

Navigation Updates

Release 24.3 brings you a revamped sidebar and menu navigation. Here's a few updates on navigation changes in Release 24.3.

Global and Folder Level Navigation

The Release sidebar has been revamped, both at the global and folder levels, for better navigation. We have made the order and grouping of navigation items more consistent. That means that some of the links can now be found in different places. We realize that these changes always take some getting used to, but we hope the grouping and consistency will make navigation easier in the end.

Here's the top level sidebar categories for easy navigation.

• The Overview section provides quick access to the building blocks of Release such as the folders, tasks, and workflow catalog.
• The Releases section includes links to access templates, releases, and related resources.
• The Deployments section groups deployments, applications, and environments.
• The Configuration section lets you access connections, triggers, and global variables.
• The Insights section lets you access analytics and reports.

Note: The default page when you select a folder is now Releases (previously it was Templates).

Release List and Calendar Tabs

The global Releases page has two new tabs—List and Calendar—to list all the releases and the release calendar respectively.

Navigating Into Subpages

When going into a section with subpages, we now use a pop up menu to select the landing page. This makes it easier to go directly to the desired page, rather than to go through a default landing page for that section.

Release Flow

We have cleaned up the Release flow view by moving much used elements to the sidebar on the left.

• The info section on top contains title, status, progress bar and link to the template it was created from. When on a template, it has a link to all releases created from it.
• The different views for Flow, Code, Table and Planner are now in the sidebar under the View section.
• Other items have been grouped and reordered for a more consistent navigation

For more information, see Release Flow Editor.

Move Folders

It's now possible to move folders. Use this feature to reorganize your folder tree, for example to reflect updates in your organization or for a more logical grouping.

You can now move folders that include templates, releases, triggers, connections, etcetera without conflicts, but some restrictions do apply. For example, if a template in a folder references a connection from another folder that is not available on the destination folder it will not be possible to move a folder.

For more information, see Move Folder.

Limitation:

• Folders containing releases and triggers that inherit configurations from other folders cannot be moved.

If parent folder connections are used and the current parent folder will no longer be the parent after the move: the move fails, and connections will need to be adjusted manually. Additionally, a folder cannot be moved into itself or any of its subfolder to prevent recursive structures.

Activity Log Makeover

The Activity Logs pages for releases, templates, workflows, delivery patterns, deliveries, and triggers have been updated with several enhancements.

UI Updates

• By default, all activities are displayed with the most recent entries at the top, eliminating the need to manually select the Category filter.

• Key actions are highlighted for easier identification, with an Important toggle that flags significant changes such as flagged tasks, deleted or skipped task, started phase, release or workflow, etc.

• Color-coded tags (pills) help differentiate between completed, failed, and skipped items.

  

Quick Access

You can now directly navigate to tasks, releases, templates, and deliveries by clicking the links in the Target column.

Improved Search

• Search activities by ID (task, release, phase, template, etc.), user name, or activity message.
• Additional filters allow you to refine the search results. You can filter by activity type (e.g., failed or skipped tasks, changed release variables, etc.) and by user or system, with the option to select multiple values.

Changes in Activity Log Messages

• Message text has been updated. For more information, see here.
• Longer messages (including script tasks) display up to 1000 characters and are truncated if they exceed this limit. Both the old and new text are counted in the message length.

Accessing the Activity Log

• You can access the Activity logs for a specific item from multiple locations. For example, Task Activity logs can be opened from the Release or Template Flow page task card or Task drawer context menus. Clicking this option leads to the Activity logs page, pre-filtered by the specific task ID.

  

Task Drawer Enhancements

The Task Drawer UI has been enhanced to improve the user experience.

Template Drop-down for Create Release task

In the Create Release tasks, the accessibility of searching and selecting templates from the Template drop-down has been enhanced. Previously, the drop-down only listed template names in a single, flat list. Now, templates are grouped under folders, making it easier to identify and select the appropriate template.

For more information, see Create Release task.

Documentation for Task Types

To access the documentation of the task type directly from the task, a new help icon button is added to the top header of the Task Drawer. This functionality is implemented across all tasks within Release, including those from plugins. For instance, upon accessing the Task Drawer of the Create Release task and clicking this help icon button, you will be directed to the corresponding documentation for the Create Release task.

Tip: Additionally, you can add links to your documentation site for custom plugins.

A new property called documentationPage is added to the synthetic.xml to define the documentation page link of the task.

Here's a sample:

<type-modification type="xlrelease.CreateReleaseTask">
    <property name="documentationPage" required="false" hidden="true" default="how-to/create-a-create-release-task.html"/>

Release Flow Enhancements

Updates to Task Cards

All tasks now show their task type. Previously, this was available only for automated tasks.

For Manual task statuses:

• Planned, In Progress, and Failed: displays the user or team assigned to the task. Skipped, Skipped in Advance, Completed, Completed in Advance, and Aborted: displays the user or team who made the status change.

For Automated task statuses:

• Planned, In Progress, and Failed: displays the assigned user or team, even if the task is automated. If the task fails, the assigned user or team is shown to facilitate the task recovery.
• Skipped, Skipped in Advance, and Aborted: displays the user or team who made the status change.
• Completed: No user or team information is displayed, as the automated task is completed and no further action is needed.

A New Way to Add Tasks

In the Release and Template flow pages, you can now search for tasks by typing the task type or task group name while adding a task. This makes adding tasks easier especially when you have a long list of tasks to select from. Keyboard shortcuts are supported, so you can conveniently add a bunch of tasks using the keyboard only.

To preview the complete list of available tasks, use the "All types" functionality. This will display the task tree menu from previous versions.

Change Task Type

There is a new dialog to change a task's type. This functionality is available from the context menu on the task card; the context menu of the task drawer and as a context menu in the table view.

This dialog displays the current type of the task. In the New type drop-down, select the type of task for which you want to change to and click Change type.

UI and Functional Enhancements

Here's some UI and functional enhancements for a better user experience.

Task Page Filter Updates

• Search button is no longer available now in the Tasks page.

• Filters have been reorganized based on its usage frequency, with the most used ones now listed first. The free text search and Tags filter are always displayed.

• Pagination is moved to the bottom now. The tasks per page can be selected using the drop-down. It can be 10, 20, or 50. The default value is 20.

  

Personal Access Token (PAT) Updates

In the Personal access tokens page, a new column titled Expires in is added to provide visibility into the token expiration timelines.

Note: Release administrators now have the option to set a 45-day expiration period for Personal Access Tokens, in addition to the preset options of 7 days, 30 days, 60 days, 1 year, and No expiry.

The following list provides information about how the token expiration is notified:

• If the token has no expiry, the Never pill is displayed.
• If the expiration date is greater than 5 days, the number of days before the expiration is displayed.
• If the expiration date is less than 5 days, a warning pill is displayed with the number of days remaining for expiration.
• If the expiration date is less than 24 hours, a warning pill is displayed with the message stating Less than 24 hours.
• If the expiry date is passed, a caution pill is displayed with the message stating Expired.

For more information, see Personal Access Token for Authentication.

Support for Connection Reference Variables at Folder and Global Levels

Connection reference variables can now be created and used at both the folder and global levels. Previously, reference variables were limited to release variables within folders. With this update, connections such as Jenkins servers can be referenced globally, offering greater flexibility across templates.

• Connection reference variables can now be created at the global level, which lets templates reference these variables across all templates, not just within a specific folder.
• Reference variables for connections, like Jenkins servers, are now available at both the global and folder levels.
• Connection reference variables are compatible with version control, making it easier to track changes and apply updates across templates.

For more information, see Configure Reference Variable Connection.

Copy Task API

This enhancement lets you copy the tasks via the API between templates, releases, workflow templates, and workflow executions.

When copying tasks:

• Missing release variables in the destination will be re-created.
• Any missing folder variables or folder connections will be reported in the comments of the copied task.
• Release variables with value providers may need extra attention when copied between containers.
• You must have the appropriate permissions for both the source and destination when copying a task between releases.

Additionally, the API lets you copy tasks across different containers. This includes copying tasks within the same release, different releases in the same folder, or releases in different folders. You can still use the same API call for this feature: Copy a task to a specific position inside a container.

The system automatically checks for any missing data during the copying process. If it cannot replicate certain data, it adds a comment to the copied task to clarify what is missing.

.

Folder Information in Jython Scripts

The Jython Script task got additional APIs to get access to folder data, without the need of setting a "Run as" user on the release. This makes it to retrieve folder information.

• The release.getFolder() method returns the folder associated with the current release, including its basic information like the folder name.
• The folder.getParentFolder() method provides access to the parent folder, enabling seamless tracing of the entire folder chain without requiring additional API calls.

Permission Updates

Here's what's new and changed with permissions in Release.

Runner Permission

The Runners page under Settings is now available to users with the global Runner registration permission.

For more information, see Release runners overview.

View Teams and Permissions

A new folder level permission called View teams and permissions is added to the Teams & permissions page. This permission only allows you to view the contents of the Teams & permissions page. It does not allow you to modify the content of this page.

Additionally, the previously used two folder-level edit permissions are renamed as follows:

• Edit folder security to Edit teams and permissions
• Edit folder teams and permissions to Restricted edit of teams and permissions

These permissions allow you to modify the content in the Teams & permissions page.

API, SDK and Scripting

Improved Error Handling in GO SDK

This release enhances error handling in the GO SDK HTTP client, providing developers with more detailed insights into HTTP request and response management. Key improvements include:

• Full HTTP Response Visibility: The HTTP client now returns the entire HTTP response, providing a comprehensive view that aids in diagnosing and managing errors effectively.

• Enhanced Redirection Handling: Added support for 3xx (redirection) status codes. When a 3xx response is encountered, an alternative approach is recommended for more effective redirect handling.

• New Method for Custom Requests: The doSendHttpRequest method now enables sending HTTP requests with custom configurations and headers, returning the full HTTP response for added flexibility in request handling.

For more information, see Go SDK.

System Settings

Advanced Caching Settings

As a release administrator, you can manage cache settings to optimize system performance. Enable or disable specific cache options to control how data is temporarily stored and retrieved, improving load times and efficiency when enabled. For more information, see Enable Advanced Cache Settings

.

Limits for Live Log Entries

The log truncation and debugging mechanism helps you manage live log entries that you see in the Task Drawer's Activity tab during task execution.

Log truncation lets you set a maximum size limit for live logs. Once enabled, the system automatically trims logs when they reach the set limit, preventing the accumulation of too many log files on the system.

For more information, see Task execution log settings.

Product Installation and Configuration

Configure DNS TTL

Release 24.3 brings you the security.properties configuration file, which you can use to override the default JVM settings.

Release uses the JVM's DNS cache settings by default. The default JVM setting is set not to expire cached addresses. This may cause network problems with some services such as the Digital.ai Platform.

To overcome such issues, the DNS cache expiry is set to 30 seconds by default (the networkaddress.cache.ttl=30 property has been added by default to the security.properties file).

You can increase or decrease the DNS TTL per your requirements in the security.properties file.

Store Reports and Task Logs on S3

You can now choose to store your reports and task logs in the cloud—Amazon S3.

• Simplified Storage: You can now store reports and logs directly on Amazon S3. This eliminates the need for shared filesystem storage, reducing configuration complexities and costs associated with solutions like NFS and RWX storage classes in Kubernetes.
• Config File Updates: Installation is simplified with a configuration file that sets everything up automatically.
• Custom URI Scheme: File entries use a unique URI scheme, ensuring they are compatible with future dynamic configurations.
• Manual Migration: YOu can use the AWS CLI to move existing files to S3.

For more information, see:

• Store Reports and Logs on S3—JVM Cluster
• Store Reports and Logs on S3—Kubernetes

Docker 'latest' Images

The implicit 'latest' version tag is no longer supported for Deploy and Release docker images. To use Docker images, it is now required to specify the release version, for example 24.3. When using a release version without patch number, it will download the latest maintenance release. For example, 24.3 may download the latest version24.3.1.

Correct

docker pull xebialabs/xl-release:24.3

No longer supported

docker pull xebialabs/xl-release

Kubernetes Installation Operator Enhancements

Here's what's new and changed with the Kubernetes Operator-based installer.

RedHat Certified OpenShift Operator

We are happy to announce that our Kubernetes Operator for Release and Deploy is new certified by RedHat for use in OpenShift installations.

The Digital.ai Release operator is available in the RedHat catalog

For more information, see Installation with Openshift Certified Operator.

Kubernetes 1.30 Support

Digital.ai Release supports installation on plain multi-node Kubernetes clusters, on-premise, for versions 1.20 to 1.30 (1.30 is supported from Release 24.1.10 and later).

Slim image and setting Up JDBC and MQ Drivers

Most third-party driver jars are not shipped with the product and need to be configured separately.

There is a new way to configure third-party driver jars. This makes it easier to manage them in a controlled way, without interfering with the installation and plugin jars.

For more information, see Setting Up JDBC and MQ Drivers.

Note: Supported from Release 24.1.4 and later.

We are also offering new image: the slim type. This original image contains a few drivers, like the default PostgreSQL one and the embedded ones for trial installations. The slim image does not container any drivers at all. This has the advantage that security scans will not fail on unused drivers, at the expense of having to install a driver jar manually.

Air-gapped Installation

We have enhanced support for running Release in air-gapped Kubernetes environments.

For more information, see Air-gapped Installation of Application Images.

Note: Supported from Release 24.1.2 and later.

Configure Read-only Root File System

Release operator-based installation now supports the readOnlyRootFilesystem setting in containerSecurityContext, enabled by default to improve security. By setting readOnlyRootFilesystem=true, the container root file system mounts as read-only, preventing any modifications at the root level. This setup is especially useful for users who need strict control over writable directories.

With readOnlyRootFilesystem active, unauthorized changes—such as rewriting executables or altering specific files—are blocked. Even with root access, users cannot modify files in designated read-only directories. Only certain folders, like cache, remain writable, helping maintain secure, controlled operations.

Support Non-admin User of Cluster

A non-admin user in a Kubernetes cluster can now install Release without needing admin-level permissions on the cluster. Key changes include:

• Namespace-Specific Resource Creation: Resources can only be created in specific namespaces, removing the need for wider cluster permissions.
• Restrictions on Cluster Resources: The installation skips creating cluster-wide resources like IngressClass and Route, keeping everything contained within the specified areas.
• No Security Context Constraints (SCC): SCC creation is not required, which helps prevent privilege escalation and improves security for users with limited permissions.
• Support for Random UIDs: The installation works with containers that use random UIDs, providing more flexibility for different cluster environments.

Plugins and Integrations

Here's what's new and changed with container and legacy plugins.

Added Support for JFrog Artifactory for Plugin Repository

JFrog Artifactory can now be used as a proxy for plugins that are currently hosted on Nexus, allowing it to act as a mirror for your plugin repository in secure, air-tight environments.

For more information, see:

• Using Artifactory to store plugins
• Migrate from Sonatype Nexus repository to JFrog Artifactory

Argo CD Plugin

• In the Create Application task, the Upsert and Validate toggles are added.
• In the Add Repository task, the Project Name field is added.
• Helm charts can now be deployed using Argo CD tasks.
• In the Wait for Status task, added capability to specify the retry counts and wait intervals between retries.
• The Argo CD Create Application task now includes new fields for Kustomize configurations. Kustomize is a configuration management tool for Kubernetes, making it easier to manage and customize your Kubernetes resources.
• Added support for Helm parameters.
• Added lookups for chart, version, and revisions.

For more information, see Argo CD Plugin.

Ansible Plugin: Container and Legacy

Ansible scripts are now directly accessible from a GitHub server path. These scripts are managed in GitHub, and you need to provide the script file path in the Ansible task. You can connect to the GitHub server, fetch the script file, and execute it on the Ansible server.

For more information, see Ansible Container Plugin.

Bamboo Plugin

Added implementation to pull only the relevant projects.

For more information, see Bamboo Plugin.

Bitbucket Plugin

New tasks added for Bitbucket Cloud:

• Create Tag
• Tag Release

New tasks added for Bitbucket Server:

• Check Branch Existence
• Get Branch Restrictions

For more information, see Bitbucket Plugin.

CheckmarxOne Plugin

New tasks added for CheckmarxOne:

• GIT Scan Trigger
• SCA - Check Compliance
• SAST - Check Compliance
• Additionally, a new tile is added for CheckmarxOne: CheckmarxOne Scan Summary

For more information, see Checkmarx Plugin.

GitHub Actions for Release (GitHub Marketplace)

The Digital.ai Release GitHub Actions enables the creation of a new release and start it on the Digital.ai Release. It facilitates seamless integration between your GitHub repository and Digital.ai Release, automating release management processes. Go to this page to get the latest version.

For more information, see Release GitHub actions.

GitLab Plugin

New tasks are introduced:

• Revert Commit task is added to revert a specific commit in GitLab.
• Create Pipeline task is added to create a new pipeline in GitLab.
• Additionally, modified the Query Pipeline Status task to take the Pipeline Id as input, which is the output of Create Pipeline task.

For more information, see GitLab Plugin.

Hashicorp Vault Plugin: Container and Legacy

In the Connections page, added a custom mount path field for all the authentication methods.

For more information, see HashiCorp Vault Plugin.

Jenkins Plugin

• Scan Multibranch task is added to scan multiple branch pipelines. This triggers the build job without the branch name.
• Fixed issues where 401 status from Jenkins was running in infinite loop instead of throwing an error.

For more information, see Jenkins Plugin.

MongoDB Cloud Plugin

The MongoDB plugin lets you write your own tasks and run them against a local or cloud MongoDB database.

• The following tasks are available:
  • Insert data
  • Get data
  • Insert and get data

This plugin requires a Release Runner to be available.

For more information, see MongoDB Cloud Plugin.

ServiceNow Plugin

In the wait for status task, support is added for waiting for one of the multiple statuses.

For more information, see ServiceNow Plugin.

OpenShift container Plugin

You can now migrate from the OpenShift legacy plugin to container-based plugin.

For more information, see OpenShift Container Plugin.

SonarQube container Plugin

You can now migrate from the SonarQube legacy plugin to container-based plugin. The tasks in the container-based plugin have the following improvements:

• Added lookups for all the required fields in the tasks and reordered them based in their importance.
• Check Blocking Violations task in legacy plugin is renamed to Check Violations (Container) in container-based plugin.
• The Blocker Violations, Critical Violations, and Major Violations fields in the Check Blocking Violations task legacy plugin is now replaced with High Violations Threshold and Medium Violations Threshold fields in the Check Violations (Container) container-based plugin.
• Improved the error handling.
• New connection page added and only bearer-token is supported.

For more information, see SonarQube Container Plugin.

SonarCloud container Plugin

You can now migrate from the SonarCloud legacy plugin to container-based plugin. The tasks in the container-based plugin have the following improvements:

• For SonarCloud container-based plugin, in the Resource field, now the project name and the organization name are displayed. Earlier, with SonarCloud legacy plugin, only project name was displayed.
• New connection page added and only bearer-token is supported.

For more information, see SonarCloud container plugin.

Change and Risk Prediction (CRP) Plugin

Added the Digital.ai Release change and risk prediction plugin to predict software change failures with the Get Risk Prediction task. For more information, see Change and Risk Prediction (CRP) Plugin.

VSTS/TFS Plugin (Azure DevOps)

You can now handle partial success and failure in Azure Build pipelines more effectively. The pipeline outputs detailed results, helping you identify which tasks succeeded or failed for easier error tracking.

• You can now retrieve the BuildResult variable for tasks with Partially Succeeded or Failed statuses.
• Previously, BuildResult only contained Succeeded or was empty in failure cases​.

For more information, see VSTS/TFS Plugin.

Bug Fixes and Field Incidents

Bug Fixes and Field Incidents—24.3.2

• D-37405 - Fixed an issue where creating a Jython task from a Groovy script or Release file added extra indentations, causing the task to fail.

Bug Fixes and Field Incidents—24.3.1

This version was skipped, and 24.3.2 was released in its place.

Bug Fixes and Field Incidents—24.3.0

• D-33514 - Fixed an issue that prevented folder from expanding.
• D-33888 - Fixed an issue where the updates made to the variables in the User Input task using the old Task modal view were not being logged in the xl-release.log file or in the corresponding Release's Activity logs.
• D-34138 - Fixed an issue where, when the password autofill feature in Chrome is enabled, it removes the variables used in the Create Release screen.
• D-34658 - Fixed an issue with the User Input task that was not getting completing despite all the required fields being filled.
• D-35090 - Fixed an issue with the OpenShift operator and XL CLI-based installations that was preventing the PostgreSQL pod from being generated.
• D-34847 - Fixed an issue where a Release user with only folder#view permissions on a folder could manage the permissions for that folder via XL CLI and grant themselves higher-level access.
• D-35126 - Fixed an issue where exporting a release template as a Release file (Groovy) and then attempting to import the same template would result in an error.
• D-35188 - Fixed an issue that prevented scheduled environment reservation tasks from starting at the specified time.
• D-34492 - Fixed an issue that prevented Release templates from using variables created earlier as part of other templates.
• D-33777: Fixed an issue where variable mapping would disappear when using xl-cli to create and apply YAML files, disrupting GitOps workflows.
• D-35612: Fixed an issue that prevented saving a connection with a map_string_string property when the Properties field was left blank.