Explorar el Código

Update content for SonarQube 2026.1.0 Release (#2650)

Carmine Vassallo hace 2 meses
padre
commit
6fa1528cd9
Se han modificado 1 ficheros con 4 adiciones y 2 borrados
  1. 4 2
      sonarqube/content.md

+ 4 - 2
sonarqube/content.md

@@ -29,7 +29,7 @@ To quickly run a demo instance, see Using Docker on the [Try Out SonarQube](http
 
 ## Installation
 
-> **Multi-platform support**: Starting from SonarQube `9.9`, the docker images support running both on `amd64` architecture and `arm64`-based Apple Silicon (M1).
+> **Multi-platform support**: Starting from SonarQube `9.9`, the docker images support running both on `amd64` architecture and `arm64`-based Apple Silicon.
 
 For installation instructions, see Installing the Server from the Docker Image on the [Install the Server](https://docs.sonarsource.com/sonarqube-server/latest/setup-and-upgrade/install-the-server/installing-sonarqube-from-docker/) page.
 
@@ -37,7 +37,7 @@ To run a cluster with the SonarQube Server Data Center Edition, please refer to
 
 ### Long-Term Active (LTA) versions
 
-[LTA](https://www.sonarsource.com/products/sonarqube/downloads/lta/) refers to the version of SonarQube Server that will stay active for a longer period of time. Currently, `2025.4` is the latest LTA version and should be used when LTA version is preferred. To install the latest LTA, you can pull one of the `2025.4-lta-<edition>` tags.
+[LTA](https://www.sonarsource.com/products/sonarqube/downloads/lta/) refers to the version of SonarQube Server that will stay active for a longer period of time. Currently, `2026.1` is the latest LTA version and should be used when LTA version is preferred. To install the latest LTA, you can pull one of the `2026-lta-<edition>` tags.
 
 ## Configuration
 
@@ -67,6 +67,8 @@ We recommend creating volumes for the following directories:
 -	`/opt/sonarqube/logs`: contains SonarQube logs about access, web process, CE process, Elasticsearch logs
 -	`/opt/sonarqube/extensions`: for 3rd party plugins
 
+Beginning with SonarQube Server `2026.1`, the use of the Java Attach API for ElasticSearch 8.x initialization creates socket files in the hardcoded and unchangeable path `/tmp/.java_pid<PID>`. It is essential to ensure that SonarQube Server processes have both read and write access to the `/tmp/` folder to function correctly.
+
 > **Warning:** You cannot use the same volumes on multiple instances of SonarQube.
 
 ## Upgrading