Release Manual 8.5.x

    Upgrade instructions

    XL Release 7.5.0 shipped with a new database backend. To upgrade to this version, a separate Migrator tool needs to be run.

    For detailed instructions, refer to Upgrade to XL Release 7.5.

    Migration to the new database is only supported from XL Release versions 7.0, 7.1 and 7.2. If you are on a previous version of XL Release, you need to upgrade to 7.0 first.

    Important: If you plan to skip versions when you upgrade, ensure that you read the version-specific upgrade notes for each intermediate version. You may be required to perform manual actions as part of the upgrade.

    If you are upgrading from XL Release version 8.0.x, make sure you view the release manuals for XL Release 8.1.x and XL Release 8.2.x.

    XL Release 8.5.1

    XL Release 8.5.1 release notes

    Bug fixes

    • [REL-7017] - Script output logged in work directory not cleaned even after release is completed/archived
    • [REL-7759] - Compliance tiles are broken

    XL Release 8.5.0

    XL Release 8.5.0 is a long-term support (LTS) version that will be supported for a year after it is superseded by the next long-term support (LTS) version. Short-term-support (STS) versions do not receive maintenance releases. For more information, see Short-term support/Long-term support policy.

    XL Release 8.5.0 new features

    Manage environment bookings and resolve conflicts

    Release Engineers and Environment Managers now have more extensive options for managing environment bookings and application deployment windows in an easy-to-use calendar interface that is fully integrated with release processes. XebiaLabs checks for environment bookings before executing application deployments, so teams can identify and resolve conflicts early, before the deployment fails. This feature is available as beta functionality. For more information, see Scheduling environments.

    Enhanced release variables

    Release variables have been enhanced with support for auto-completion of variable values in release properties, phases, tasks, and dashboards, and with support for nesting variables inside other variables. In addition, the new special variable ${release.url} is automatically available for use in all releases. For more information, see Variables in XL Release

    Compliance and security

    New security and compliance tiles enable Release Managers and DevOps Engineers to ensure that applications meet IT compliance requirements and helps them identify applications that are failing to meet security standards. This gives the team a complete overview of test results from the static application security testing (SAST), dynamic application security testing (DAST), and open source security management (OSSM) tools in their release pipelines. Combining test results from across the pipeline in a single dashboard helps preserve the chain of custody of a release and makes it easy for DevOps teams and Security Officers to review results, identify trends, and make decisions about security findings.

    The following tiles have been added: SonarQube, Fortify SSC, Fortify on Demand, Checkmarx, and Black Duck.

    Reporting

    Teams can now create folder-level dashboards that show detailed data about running and completed releases in a particular folder. Folders are often used to organize projects, so this feature allows teams to set up dashboards that cater to their specific needs; they can focus on the release, deployment, security, and compliance data that is most relevant for them.

    You can create and customize deployment and release statistics dashboards from templates, or create a dashboard from scratch. For more information, see Dashboard templates.

    The following deployment titles have been added:

    DevOps as Code

    DevOps As Code provides an alternative way for developers and other technical users to define deployment packages, infrastructure, environments, release templates, and more, using YAML files that they can store in source control with the application code.

    With DevOps As Code, development teams can use the XebiaLabs DevOps Platform by adding a YAML file to their development project and applying it using the XebiaLabs CLI. The DevOps as Code feature automatically creates the configuration items that are required and starts the release pipeline. For more information, see Getting started with DevOps as Code.

    The XebiaLabs CLI

    The XebiaLabs command-line interface (CLI) enables development teams to apply YAML files to the XebiaLabs DevOps Platform to create configuration items, releases, and more. The XL CLI can also export data as YAML files from both XL Release and XL Deploy. Teams can get started with the DevOps as Code using the data they have already defined in the XebiaLabs DevOps Platform.

    You can automatically invoke the XL CLI from Continuous Integration (CI) pipelines running in tools such as Jenkins, Azure DevOps, and TravisCI. You are not required to download and install a plugin. An XL CLI command in the CI pipeline can apply YAML files and kick off releases in the XebiaLabs DevOps Platform. For more information, see Using the XL Command Line Interface.

    Implement best practices using blueprints

    The XL CLI includes support for blueprints that guide developers through a process that automatically generates the XL YAML files for their application. A blueprint asks the user a short series of questions about their application and the type of environment it requires. The CLI uses the answers to generate everything a development team needs to get started with XebiaLabs: YAML files to define configuration items and releases and special configuration files that manage sensitive data such as passwords.

    Organizations can use the blueprint framework to create blueprints that reflect their own standard application, infrastructure, and environment profiles. XebiaLabs provides sample blueprints with best practices built-in that you can use to migrate from on-premises infrastructure and legacy middleware to cloud-based platforms. For more information, see Getting started with blueprints.

    Contact XebiaLabs Support if you have hotfixes

    If you have hotfixes installed, contact the XebiaLabs support team before upgrading.

    XL Release 8.5.0 release notes

    New features

    • [REL-4292] - Support variable references in variable values
    • [REL-5172] - Searching releases should not be limited to a single ReleaseStatus group
    • [REL-6798] - Atlassian CROWD integration with XL Release
    • [REL-7083] - Special ${release.url} variable
    • [REL-7087] - Create DeploymentTaskFacet
    • [REL-7197] - Create tables using markdown
    • [REL-7351] - [API] Support all variable types when starting a release
    • [REL-7355] - Provide variable completion in text fields
    • [REL-7373] - Implement application configuration screen
    • [REL-7388] - Render hyperlinks in Task status line and show when completed
    • [REL-7400] - Implement logical environments
    • [REL-7401] - Add stages to associate environments
    • [REL-7402] - Provide new global permission for Environment Manager
    • [REL-7410] - Create Scheduling screen to show environment reservation
    • [REL-7411] - Add new environment reservation
    • [REL-7440] - Ability to customize HikariCP configurations
    • [REL-7457] - Additional HikariCP settings for cluster membership connection pool
    • [REL-7465] - Storage for deployment events
    • [REL-7497] - Markdown text tile
    • [REL-7521] - 2 Dashboards to be provided Out-Of-the-Box on folder level and Global level
    • [REL-7526] - Retrieving User activity data
    • [REL-7538] - Update Releases Overview page, select multiple release statuses
    • [REL-7546] - Deployments: Implement generic deployments query mechanism
    • [REL-7547] - Deployments: Create latest application versions tile
    • [REL-7548] - Deployments: Create the deployments tile (doughnut chart)
    • [REL-7552] - Allow reporting for completed/aborted but not archived releases
    • [REL-7553] - Deployments: Create the deployment success rate tile %
    • [REL-7554] - Deployments: Create the deployments activity tile
    • [REL-7555] - Deployments: Create total deployments tile
    • [REL-7556] - Deployments: Create space consuming tile
    • [REL-7570] - Check environment availability on task details
    • [REL-7608] - Add variable value provider for environments and applications
    • [REL-7610] - Don't query nexus to confirm existence of plugin jars. Presence in aggregated metadata is enough.
    • [REL-7636] - Make reservation editable
    • [REL-7641] - Add Filters to reservation

    Improvements

    • [REL-5123] - Use multiline strings in Xfile export
    • [REL-7231] - Ask for confirmation when user changes template on create release task
    • [REL-7251] - Make add task menu longer
    • [REL-7387] - Optimize archive database upgrade
    • [REL-7425] - Create release task doesn't show folder component if user does not have view permission for any folder
    • [REL-7491] - Use planner (FE or BE) for phases in calendar view
    • [REL-7593] - Adding icon to JIRA tasks

    Bug fixes

    • [REL-3111] - Forbidden access error when opening start release task with a template for which user doesn't have view permission
    • [REL-5717] - xlr-jenkins-plugin task should not restart build on retry if Jenkins build already started
    • [REL-7062] - Error while opening a "Create release task" if referencing a secured template/secured folder
    • [REL-7252] - Output of script task is logged three times
    • [REL-7258] - Thread deadlocks on upgrade to 8.2.0
    • [REL-7390] - Create Release Task produces non portable DSL for folderId
    • [REL-7391] - Error Transaction rolled back because it has been marked as rollback-only saving version from XL Release using mySQL for db
    • [REL-7397] - Task with huge DSL script hangs in XL Release 8.0
    • [REL-7427] - OIDC Plugin missing license check for APIs
    • [REL-7435] - Abort On failure release property is not taking value from triggered template "Abort On failure" property
    • [REL-7450] - [SCM] NPE when trying to export attachments on some templates
    • [REL-7462] - Task status Line - XL Deploy task box size changes after it completes on release flow view
    • [REL-7485] - PK violation when creating release from moved template (to different folder) with customized dashboard
    • [REL-7500] - Search on releases fails because of class exception
    • [REL-7535] - JavaScript injection using variables in markdown description
    • [REL-7540] - Cannot create releases from a template inside a folder without folder#edit
    • [REL-7543] - xlr-relationship-plugin libraries overrides the dashboard libraries in XL Release
    • [REL-7557] - Do not use components with known security vulnerabilities
    • [REL-7579] - AES Encryption without using Initialization Vector (IV)
    • [REL-7590] - Comments are getting truncated after upgrade to 8.2.0
    • [REL-7592] - Activity logs do not show changes to Groovy script task
    • [REL-7647] - Do not use cursors when upgrading in postgresql
    • [REL-7736] - Activity log is not captured for some actions in a task