Release notes for DevOps Loop 2025.06 (1.0.2)

This document includes product description, information about installation instructions along with the contact information of IBM Customer Support. You can also find the known issues identified in this version of IBM® DevOps Loop.

Product description

DevOps Loop is a cloud-based continuous integration platform. DevOps Loop is built on modern, cloud-native technologies that enables product teams to plan, code, test, and deploy the applications. DevOps Loop provides a holistic view of the progress in the DevOps cycle. For more information about the platform, see Overview of DevOps Loop.

What's new

You can find information about the features introduced, enhancements, or other changes in DevOps Loop. See What's New.

Product download and installation

If you have purchased the licenses to use the product, you can obtain the key to the IBM Entitled Registry from My IBM Container Software Library and download the entitled software packages.

For instructions about installing the product software, see Installation of DevOps Loop.

Known issues

For the list of known issues that are identified in this version and the previously published known issues that are still applicable, see Known issues.

Contacting IBM DevOps Automation Support

  • For contact information and guidelines or reference materials that you might need when you require support, read the IBM Support Guide.

  • For personalized support that includes notifications of significant upgrades, subscribe to Product notification.

  • Before you contact IBM DevOps Automation Support, you must gather the background information that you might need to describe your problem. When you describe a problem to an IBM DevOps Automation Support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
    • What software versions were you running when the problem occurred?
    • Do you have logs, traces, or messages that are related to the problem?
    • Can you reproduce the problem? If so, what steps do you take to reproduce it?
    • Is there a workaround for the problem? If so, be prepared to describe the workaround.