Release notes support the installation of the latest product version. For additional information see the Installation Guide.
Latest Release details
Statements on Common Vulnerabilities and Exposures
Cirata constantly monitors the possible impact of common vulnerabilities and exposures on all its products. See the Cirata Community website for the latest ALM Product CVE Statements.
Release 3.9.0 (Latest release)
The 3.9.0 release of Gerrit MultiSite contains support for Gerrit 3.9.10 including some later fixes back-ported into this release.
Version: 3.9.0 (3.9.10-RP-1.14.0.1)
Release: 2025-07-08
Important Information
The Gerrit MultiSite 3.9.0 release has added the capability of enabling current Cirata Gerrit MultiSite customers to upgrade to this version as easily as possible. As long as the customer is running a version of Gerrit MultiSite that is post-NoteDB migration (i.e. either releases 1.10, 1.11 or 3.7.0) then this release will enable an upgrade. Customers are encouraged to contact Cirata support for more details.
The 3.9.0 release enables a simplified upgrade process from 2.16 post-NoteDB migration (and above) up to 3.9:
-
There is no need to stop at Gerrit 3.5 to run the "copy approvals" migration. The installer will automatically detect and run the "copy approvals" migration when applicable. However, there are critical details that you need to understand in order to plan a successful upgrade from prior Gerrit versions. Please contact support for this information.
-
The installer will check and update the "gerrit.config" file to use JDK 17.
Supported Operating Systems
-
Alma Linux 8, 9
-
Debian 11, 12
-
Oracle Linux 8, 9
-
RHEL 8, 9
-
Rocky 8, 9
-
SLES 15
-
Ubuntu 20 LTS, 22 LTS
Fixed Issues
GER-2244 Web_sessions cache replicated events are now supported
In prior releases the web_sessions cache replicated events were intentionally surpressed. While the default behavior is still off (like prior releases), you can now configure them to be on and a new login session created at one site will be propogated to the other sites. Please contact support if you need to configure these events on.
GER-1981 Repositories on NFS can now be completely removed
In prior releases a file descriptor was left open in a JGit cache which prevented complete removal of a repository located on NFS storage due to NFS file system semantics. This caching mistake has been corrected and the delete-project plugin can now safely remove Gerrit repositories located on NFS storage without any hiccups.
Known Issues
| Note Well: 'Reftable' based repositories are not currently supported. They will be supported in a future release. |
GER-2347 Conflicting setting in the its-jira configuration
In prior Cirata Gerrit MultiSite releases the its-jira plugin has a commentlink.serverRole setting that governs whether or not a node will post to Jira. If its value is VALIDATE_AND_POST then the node will update Jira; if its value is VALIDATE_ONLY then it will not. And one single node is expected to have VALIDATE_AND_POST set with all other nodes having VALIDATE_ONLY set (to avoid duplicate Jira entries).
With this release, if the gerrit.instanceId value is set on every node then its-jira will only post to Jira if the event is processed at the originating node and the commentlink.serverRole value is VALIDATE_AND_POST. Therefore, since we strongly recommend that gerrit.instanceId values be set uniquely for every node (to the Git MultiSite node.id value), then we also must recommend that customers either set commentlink.serverRole=VALIDATE_AND_POST at all nodes or, even better, remove the commentlink.serverRole configuration setting completely at all nodes (the default setting value is VALIDATE_AND_POST).
On the other hand, if you choose not to set the gerrit.instanceId value at this time, then you should leave the commentlink.serverRole as previously configured.
GER-2216 Required upgrade conversion for its-jira configuration
When upgrading from a previous Gerrit installation, if you have the Gerrit its-jira plugin installed, then you will need to convert the commentlink."its-jira".html into an commentlink."its-jira".link entry. A simple example would be if:
html = <a href=\"http://<host>:<port>/browse/$1\">$1</a>
then the conversion would be:
link = http://<host>:<port>/browse/$1
Gerrit documentation is here.
GER-1995 Webhooks core plugin behavior
The webhooks core plugin does not currently understand the difference between the "initiating site" and a "replicated-to site" for events. Because Cirata Gerrit MultiSite automatically delivers all events to all required sites, if the webhooks plugin is installed everywhere then the hooks will be fired everwhere (N-times what would be expected). For this release customers should only install the webhooks plugin on a single node (one which has visibility to all repositories). This behavior will be corrected in a future release.
Earlier product versions
Find User Guides for earlier versions in the Archive.