Version 24.2

important

To ensure that asynchronous reporting works correctly, please make sure the correct feature flag is enabled in RabbitMQ. Open RabbitMQ Management, go to the Admin tab -> Feature Flags -> message_containers_deaths_v2. If it's disabled, enable it.

important

Due to the transition to a new plugin mechanism when updating ReportPortal to version 24.2, all the plugins need to be reinstalled manually. Check out the updated plugins UI development guides.

1. What's Changed:

1. New features - Extended launches retention policy:
   We've introduced an extended launches retention policy to allow important launches to be preserved beyond the existing retention periods. Previously, all launches were automatically deleted after a set time to save storage. With this update, you can now mark specific launches as important, ensuring they are never deleted, as long as there is sufficient storage available. This feature is useful for retaining critical data for compliance, auditing, or historical analysis.

2. New integrations (Notifications) - Slack plugin and redesigned Notifications page:
   Teams using Slack can now set up Slack integration to receive ReportPortal notifications on launch event right in their Slack channel.
   More details can be found in Slack user guide and blog post.

3. New integrations (Bug Tracking Systems) - Monday plugin:
   Teams working with Monday as their BTS can now set up an integration to post and link issues from ReportPortal directly to Monday.

4. Import functionality moved to plugin:
   To provide more flexibility for launch import, the feature has been moved from the core application to a plugin. Users can now choose between the Robot and JUnit import plugins developed by the ReportPortal team, or create their own plugins to import results from other test frameworks.
   More details about JUnit import plugin.
   More details about Robot Framework import plugin.
   Guide on how to create import plugin.

5. Microseconds added to timestamps for better test items sequence tracking:
   Microseconds have been added to timestamps to enable a more accurate sequence of logs, as some logs previously had identical timestamps at the millisecond level.

6. LDAP integration improvements:
   

• PBKDF2 encryption has been added to the list of possible encryptions for LDAP.
  
• LDAP integration can now be created either with Full name attribute mode or with separate fields for First name and Last name.

7. Improved logic of launch rerun:
   User can report rerun of the specified launch with no attributes and the attributes for the initial launch will remain. If user reports rerun of the specified launch with attributes, only new attributes will be added to the launch.

2. Technical improvements:

1. Analyzer:
   Added:
   Message-through logging with Correlation ID, to ease debugging and understanding of logs.
   Updated:
   Refactoring: data-preparation logic joined and put into common place.
   Refactoring: model train logic standardised and prepared for future join.
   Lots of type annotations added.
   Fixed
   Re-train logic. Custom re-trained models for big enough projects do not affect negatively auto-analysis now.

2. Asynchronous Reporting:
   ReportPortal now features 2x faster reporting under full load, thanks to a new asynchronous reporting approach. A key update includes switching from a Direct exchange to a Consistent-hashing exchange. The retry mechanism was also revamped to focus on handling messages related to the reporting order.
   Read our latest blog post.

important

To ensure that asynchronous reporting works correctly, please make sure the correct feature flag is enabled in RabbitMQ.
Open RabbitMQ Management, go to the Admin tab -> Feature Flags -> message_containers_deaths_v2. If it's disabled, enable it.

3. Updated React to version 18.
4. PostgreSQL 16 support.
5. Updated Java to version 21 (Service-uat).

3. Bugs fixed:

1. Saucelabs:

• Issue with Mobile tests videos (run on real devices in SauceLabs) is solved.
• Error when opening "Sauce Labs" tab from log view is fixed.

2. Jira Cloud:

• Functionality to add Assignee for issue by typing its name or email (in case of full match) has been added.
• Bug with posting issue with "Parent" field is fixed.
• Bug with saving multi-select field as empty is fixed.
• Bug with creating Integration without predefine Issue Type is fixed.
• Possibility to add "None" value for fields with predefined values has been added.

3. Quality Gates:

• ‘'In progress' QG status doesn't change for merged launches, when 'New errors' rule is applied and no unique errors identified' is fixed.
• 'QG page is broken after editing Quality Gate, if it contains New failures/New error rules' is fixed.

4. TypeError occurring when switching between "New errors" and "Known errors" options on "Unique errors" page is solved.

5. "Unique bugs table" widget is fixed.

6. Bug with Retry reported as a separate step is fixed.

7. Issue with Resize widget functionality is solved.

important

We made some changes in how we handle Unique Errors. Thus behaviour on some stack traces might change.
We are going to review it in the upcoming updates to make sure that all cases are covered.

4. Enhancements Based on Community Feedback:

• #1914 Ability to exclude Skipped tests from statistics was added for Component health check widget (table view) and Component health check widget (table view).
• #2168 The limit for the dashboards per project has been increased to 3000 dashboards.
• #2219 On the Unique Errors page, error clusters have been introduced and sorted by size, allowing users to address the most impactful errors first.
• #2249 Email configuration has been improved taking into account possible ReportPortal deployment to a specified path ensuring that the links in notifications and other emails are correct.
• #2309, #2245 Logics of importing empty suites has been adjusted: Launches with empty suites can now be imported successfully. Empty suite has status 'Passed’.
• #1951 The issue with the launch description not being updated upon launch finish (when launch reporting started with no description and finished with any description) is fixed.
• #2230 Issue with parent nested step turning in failed status if child nested step processed after it's finished and has status 'skipped' is solved.
• #2120 Issue with broken links on filtered Launches page is solved.

5. CVE addressed:

Service auto-analyser:
CVE-2023-45853, CVE-2023-6246, CVE-2023-6779, CVE-2023-6780, CVE-2023-49468, CVE-2023-49467, CVE-2023-49465

Service-api:
CVE-2024-1597, CVE-2023-40827, CVE-2023-40828, CVE-2023-40826, CVE-2024-22243, CVE-2023-5072, CVE-2022-45688, CVE-2023-46589, CVE-2024-24549, CVE-2024-23672, CVE-2024-25710, CVE-2024-26308, CVE-2023-34050, CVE-2023-6378, CVE-2023-6481, CVE-2023-6378, CVE-2023-6481, CVE-2023-20883

Service-authorization:
CVE-2023-20860, CVE-2024-1597, CVE-2023-5072, CVE-2022-45688, CVE-2023-1370, CVE-2023-46589, CVE-2024-24549, CVE-2024-23672, CVE-2024-25710, CVE-2024-26308, CVE-2023-34050, CVE-2023-6378, CVE-2023-6481, CVE-2015-7501, CVE-2015-4852

Service-metrics-gatherer:
CVE-2023-45853

Service-jobs:
CVE-2024-1597, CVE-2023-46589, CVE-2024-24549, CVE-2024-23672, CVE-2023-6378, CVE-2023-6481, CVE-2024-22243, CVE-2024-25710, CVE-2024-26308, CVE-2023-34050, CVE-2023-20883

Service-ui:
CVE-2023-52425, CVE-2023-52426, CVE-2024-25062, CVE-2023-45857

6. Released versions:

Service Name	Repository	Tag
Index	reportportal/service-index	5.12.0
Authorization	reportportal/service-authorization	5.12.0
UI	reportportal/service-ui	5.12.0
API	reportportal/service-api	5.12.0
Jobs	reportportal/service-jobs	5.12.0
Migrations	reportportal/migrations	5.12.1
Auto Analyzer	reportportal/service-auto-analyzer	5.12.0-r1
Metrics Gatherer	reportportal/service-metrics-gatherer	5.12.0-r1

7. Migration Guide