REL-3493 Release SonarQube Community Build 25.1

SonarSource · Jan 7, 2025 · 964e101 · 964e101
1 parent 621c9f4
commit 964e101
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 7 deletions.
diff --git a/.cirrus/tasks.yml b/.cirrus/tasks.yml
@@ -19,7 +19,7 @@ env:
   CURRENT_VERSION: 10.8.1
   NEXT_VERSION: 2025.1
   # Must be in the format YY.MM.0.###### where ###### is the build number
-  COMMUNITY_BUILD_VERSION: 24.12.0.100206
+  COMMUNITY_BUILD_VERSION: 25.1.0.102122
 
 
 build_server_hw_template: &BUILD_SERVER_HW_TEMPLATE

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -54,4 +54,4 @@ jobs:
           - community
     uses: ./.github/workflows/release-template.yml
     with:
-      tag: ${{ matrix.tag }}
+      tag: ${{ matrix.tag }}
diff --git a/community-build/Dockerfile b/community-build/Dockerfile
@@ -14,7 +14,7 @@ ENV LANG='en_US.UTF-8' \
 #
 # SonarQube setup
 #
-ARG SONARQUBE_VERSION=24.12.0.100206
+ARG SONARQUBE_VERSION=25.1.0.102122
 ARG SONARQUBE_ZIP_URL=https://binaries.sonarsource.com/Distribution/sonarqube/sonarqube-${SONARQUBE_VERSION}.zip
 ENV DOCKER_RUNNING="true" \
     JAVA_HOME='/opt/java/openjdk' \

diff --git a/release.md b/release.md
@@ -9,11 +9,13 @@ Overview
 
 Release of a new version of the official SonarQube Server Docker images is made of several operations. (Please note that in case of a patch release that should not include the latest changes on master, you need to release from a new branch - e.g., `release/10.8.1` - and propagate the changes to master afterwards).
 
-1. set the new version of SonarQube Server (`SONARQUBE_VERSION`) to be released in the Dockerfiles. In case of community build, please remember to update `community-build/Dockerfile` only.
-2. if you are releasing a new LTA, set `CURRENT_LTA_VERSION` in `.cirrus/tasks.yml`. Otherwise, if you are releasing a Community build, set `COMMUNITY_BUILD_VERSION` only. In all the other cases where a paid edition is about to be releases, set `CURRENT_VERSION` (please note that the nightly build will fail before the public image becomes available).
+1. Set the new version of SonarQube Server (`SONARQUBE_VERSION`) to be released in the Dockerfiles. In case of community build, please remember to update `community-build/Dockerfile` only.
+2. If you are releasing a new LTA, set `CURRENT_LTA_VERSION` in `.cirrus/tasks.yml`. Otherwise, if you are releasing a Community build, set `COMMUNITY_BUILD_VERSION` only. In all the other cases where a paid edition is about to be releases, set `CURRENT_VERSION` (please note that the nightly build will fail before the public image becomes available).
 3. Update the docker hub SonarQube Server's documentation (if applicable)
-4. Update Docker Hub's SonarQube Server images
-5. add a GIT tag for the new version
+4. Add a GIT tag for the new version
+   1. If you are releasing a SonarQube Server version, you need to [Draft a New Release](https://github.com/SonarSource/docker-sonarqube/releases/new), where the name matches "SonarQube Server 2025."
+   2. Likewise, if you are releasing a Community Build, the release name should match "Community Build", followed by the month version, i.e., "Community Build 25.1".
+5. Update Docker Hub's SonarQube Server images
 
 
 Bump the version of SonarQube Server in Dockerfiles