24.2.0

☝️ Important 1:
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 2:
Due to the transition to a new plugin mechanism when updating ReportPortal to version 24.2.0, all the plugins need to be reinstalled manually.
Check out the updated plugins UI development guides.

☝️ Important 3:
Please note that the double-entry values and environments have been removed from version 24.2.0.

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.
   Learn more.

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.
   Learn more.

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.

8. New language introduced:
   Users can now utilize the interface in Spanish, and we encourage everyone to contribute to further translations or improve the existing ones.
   A special thank you to @mg-diego for his valuable contribution to the Spanish translation!

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.
   Learn more.
   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 version 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.

4. 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.

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

6. "Unique bugs table" widget is fixed.

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

8. 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.
• #1020, #36 Issue with logs sequence 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-2023-6378, CVE-202...

24.1.7

Bump the chart version for artifacthub.io

Full Changelog: reportportal-24.1.6...reportportal-24.1.7

24.1.6

What's Changed

• Update chart annotation by @raikbitters in #424

Full Changelog: reportportal-24.1.5...reportportal-24.1.6

24.1.5

What's Changed

• Update UI service image
• Update chart dependencies
• Add Makefile with common commands

Full Changelog: reportportal-24.1.4...reportportal-24.1.5

24.1.4

What's Changed

• Hotfix 24.1.4 by @raikbitters in #419

Full Changelog: reportportal-24.1.3...reportportal-24.1.4

24.1.3

What's Changed

• Global image values.
• RabbitMQ plugins.
• Helm pre-install hook for job updates.
• Image versions with critical fixes.
• Values.yaml impovmets.
• Hotfix: Update AMQP settings

Full Changelog: reportportal-24.1.2...reportportal-24.1.3

24.1.2

What's Changed:

• Increase versions for the MinIO, Service API, Service UAT, and Service Index.
• Fix base path handling for Service Index.
• Add RabbitMQ plugins.
• Fix losing volumes for the MinIO.

24.1.1

Note: This release contains breaking changes for dependent chart values.

What's Changed:

• Added support for ReadWriteMany Persistent Volume Claim to store attachments.
• Integrated Helm test functionality.
• Updated dependent charts: RabbitMQ, MinIO, and PostgreSQL to their latest versions.
• Upgraded service images.
• Fixed UAT readiness values.
• Configured Ingress path.
• Added hostAliases for UAT service to enable interaction with internal SSO servers if they cannot be resolved by host.
• Added path variables.
• Fixed various comments and documentation:
  • Updated Minikube installation guide.
  • Updated GKE installation guide.
• Added GCP-managed certificate checking.
• Added support for setting hosts as a string or array.
• Added ARM architecture support for init containers (#382).
• Changed k8sWaitFor repository.
• Split uat-secret according to Helm linter error.
• Updated reportportal/migrations image tag to 5.11.1 (ARM supported).
• Added Helm readiness test.

24.1.0

1. What's Changed:

• New feature – Immediate Auto-Analysis:
  This feature employs Auto-Analysis based on specific test cases immediately after their completion for proactive issue investigation.

• New feature – Immediate Pattern-Analysis:
  No more need to wait for the launch finish. Initiate Pattern Analysis immediately after completion of specific test cases.

• New Integration – Gitlab Plugin:
  New BTS plugin expanding ReportPortal BTS integration options for streamlined bugs reporting, issues.

• New feature – Retention Policy for Monitoring events
  Set a custom retention period for monitoring events via environmental variables to tailor data management to your organizational needs.

• Settings redesign
  Project Settings were redesigned completely, setting the stage for a whole new ReportPortal experience.

2. Small Updates:

• Change in Base for AA:
  New options for Base for Auto Analysis have been introduced.

• Enhanced Monitoring:
  Improved Filtering on Monitoring page and expanded list of events being tracked

• Enhanced Monitoring:
  Improved Filtering on Monitoring page and expanded list of events being tracked

3. Technical Improvements:

• ElasticSearch has been replaced with OpenSearch.
  Following ElasticSearch's re-licensing in version 7.11, we've transitioned to OpenSearch to uphold our focus on open-source compatibility.

Important: Migration from ElasticSearch to OpenSearch is irrevocable.

• Please, note that some of the environmental variables names are still ElasticSearch specific, but it will be corrected in the future versions.

• Service-api migration to Java 21

• Introduced JCloud provider for local file access, replacing the existing filesystem implementation:

• Added support for providing a custom salt key using secret management tool to enhance security and flexibility:

4. Enhancements Based on Community Feedback:

• #3132 Component Health Check widget improvements.

• #308 Ability to specify filter parameters in the URL has been added

• #2148 Duplicated error logs issue solved

• #2159 Option to either include skipped test into Flaky test cases table (TOP 50) widget added

• #520, #2006 Launch import improvements

• #64, #315 Service-jobs issue fix

• #1841, #1999 PR was rejected as it contained breaking changes. Instead new converter for openmetrics was added to configuration

5. CVE addressed:

CVE-2023-44487, CVE-2023-3978, CVE-2023-1436, CVE-2022-1471, CVE-2022-42003, CVE-2020-36518, CVE-2022-45688, CVE-2023-5072, CVE-2022-22965, CVE-2023-20863, CVE-2022-2297, CVE-2022-1471

6. Released versions

• All the ReportPortal services changed images to new 5.11.0 versions. Check the dockerhub.

7. Helm Chart changes

• Service API has the new pattern analysis and immediate IA configuration values.
• Service Jobs included a new CRON jobs to cleaning events values.
• ImagePullsecret for services that haven't included it before #368
• Released images
• Service Annotations added by #365 and improved.
• Allow using secret for OpenSearch in the ReportPortal Migrations Job
• Double entry disabled by the default
• Switched to OpenSearch from ElasticSearch (Note: Migration isn't required)

7. Link to Migration Guide:

• How to migrate to Reportportal v24.1 on Kubernetes

23.2.0

In this latest Helm Chart update, we've adopted a more streamlined release strategy by separating Helm Chart updates from the overall product releases. You'll now easily identify these specific updates in the GitHub release header with the tag "Helm Chart Update."

This release marks a comprehensive refactor of our Helm Chart, simplifying the installation process by ensuring that users can effortlessly install our chart along with all its dependencies. Notable additions include the introduction of migrations-waiting-init init containers for core services, designed to verify the condition of dependent services.

What's Changed:

• 🚀 New Feature: Introducing a new feature that allows to installation of all dependencies to the cluster from scratch.
• ⎈ Kubernetes Version: Now we support the latest Kubernetes version, up to 1.29.
• 🛠️ Helm Chart Refactor: The Helm Chart has undergone a significant refactor, streamlining its structure and improving overall efficiency.
• 📜 Log Streamer Sidecar: We've incorporated a new sidecar container for API audit logs to enhance log streaming capabilities.
• 🛡️ RBAC Updates: The rbac/reportportal-serviceaccount.yaml file has been updated to reflect the latest changes.
• 📖 Installation Guide: The Installation Guide has been revised to provide up-to-date instructions for a seamless installation experience.
• 🚀 Ingress Enhancements: A general Ingress approach has been implemented to support various ingress controllers. Additionally, the base path for API, UAT, Jobs, and UI services has been altered, with each service now functioning from its respective prefix. Notably, the ingress no longer cuts prefixes from routes.
• 🔄 Dependency Update: We've moved from ElasticSearch to OpenSearch 2.11.1 as a default dependency, ensuring compatibility and leveraging the latest features.

Stay tuned for more updates and improvements as we continue to enhance the functionality and usability of our Helm Chart.