Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release docs #789

Merged
merged 6 commits into from
Oct 7, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/installation-steps-advanced/FileStorageOptions.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ In ReportPortal 23.1 we can use multiple ways to store log attachments, user pic
- MinIO distributed object storage
- File system

Currently we have 2 file storage systems: **multi-bucket** and **single-bucket**.
Currently, we have 2 file storage systems: **multi-bucket** and **single-bucket**.

In the multi-bucket system structure of buckets looks like this:

Expand All @@ -38,6 +38,8 @@ To set up AWS S3 in API, UAT & Jobs services use the following variables:
- DATASTORE_SECRETKEY for AWS S3 SecretKey
- DATASTORE_REGION for AWS region

> For us-east-1 value should be **us-standard**. More information [here](https://jclouds.apache.org/reference/javadoc/2.3.x/org/jclouds/aws/domain/Region.html)

To set up the **multi-bucket** system, use the following environment variables:

- DATASTORE_BUCKETPREFIX for prefix of bucket name (‘prj-‘ by default)
Expand Down Expand Up @@ -71,7 +73,7 @@ To set the **single-bucket** system, use the following environment variables:

## File system

The file system option is used when you want to store this data in a mounted folder in the service-api or/and service-uat.
The file system option is used when storing this data in a mounted folder in the service-api or/and service-uat.

To use this option, set up environment variables like this:

Expand Down
9 changes: 7 additions & 2 deletions docs/releases/Version24.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,11 @@ Due to the transition to a new plugin mechanism when updating ReportPortal to ve
Check out the updated plugins [UI development guides](/developers-guides/PluginDevelopersGuide/PluginUIDevelopersGuide).
:::

:::important
Double entry removed. Review changes by comparing GitHub releases in [Docker](
https://github.com/reportportal/reportportal/compare/v24.1...v24.2) or [Kubernetes](https://github.com/reportportal/kubernetes/compare/reportportal-24.1.0...reportportal-24.2.0).
:::

## 1. What's Changed:

1. **New features** - **[Extended launches retention policy](/configuration/LaunchesRetentionPolicy)**: <br/>
Expand All @@ -42,7 +47,7 @@ Check out the updated plugins [UI development guides](/developers-guides/PluginD
- PBKDF2 encryption has been added to the list of possible encryptions for LDAP.<br/>
- 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**:<br/>
7. **Improved logic of [launch rerun](/developers-guides/RerunDevelopersGuide)**:<br/>
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:
Expand Down Expand Up @@ -110,7 +115,7 @@ We are going to review it in the upcoming updates to make sure that all cases ar
- [#1951](https://github.com/reportportal/reportportal/issues/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](https://github.com/reportportal/reportportal/issues/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](https://github.com/reportportal/reportportal/issues/2120) Issue with broken links on filtered Launches page is solved.

- [#1020](https://github.com/reportportal/reportportal/issues/1020), [#36](https://github.com/reportportal/agent-js-jasmine/issues/36) Issue with logs sequence is solved.
## 5. CVE addressed:

**Service auto-analyser:**<br/>
Expand Down
2 changes: 1 addition & 1 deletion docs/releases/Version5.3.5.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar_label: Version 5.3.5

# Version 5.3.5

# Bugfixing
## Bugfixing
- Fixed: [#950](https://github.com/reportportal/reportportal/issues/950) Problems with DB locks on SELECT
- Fixed: [#1231](https://github.com/reportportal/reportportal/issues/1231) Problems with data retention jobs
- Fixed: [#1269](https://github.com/reportportal/reportportal/issues/1269) Problem with an infinite load on Ctrl/Command+Click
2 changes: 1 addition & 1 deletion docs/releases/Version5.6.2.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,6 @@ sidebar_label: Version 5.6.2

# Version 5.6.2

# Bugfixing
## Bugfixing

- ReportPortal release 5.6.2 aimed at fixing Log4J vulnerabilities: [CVE-2021-44228](https://github.com/advisories/GHSA-jfh8-c2jp-5v3q), [CVE-2021-45046](https://github.com/advisories/GHSA-7rjr-3q55-vv33) and [CVE-2021-45105](https://github.com/advisories/GHSA-p6xc-xr62-6r2g)
19 changes: 19 additions & 0 deletions docs/work-with-reports/ViewLaunches.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,25 @@ Also, you can use the logs sorting by time, and filtering logs to find a certain

<MediaViewer src="https://youtu.be/_g0GW16sXGU" alt="Log Messages in our automated testing tool" type="video" />

### Timestamps

In ReportPortal version 24.2, microseconds have been added to timestamps to provide a more precise log sequence.
Previously, some logs shared identical timestamps at the millisecond level, which led to issues with log ordering.

With this update, you have the flexibility to view timestamps in two formats:

1. Date & time

<MediaViewer src={require('./img/view-launches/Milliseconds.png')} alt="Date & time" />

2. Time with microseconds

<MediaViewer src={require('./img/view-launches/Microseconds.png')} alt="Time with number of microseconds" />

You can easily switch between these options with a simple click.

The choice will be saved to `localStorage` to persist between sessions in a particular browser.

### Stack trace

On the Log view for the fast redirection to the last 5 error log messages, please click on the tab Stack trace, in this section you can find *5 last error logs".
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.