Gerrit MultiSite Release Notes

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.

The installer will check and update the "gerrit.config" file to use JDK 11.

JDK 11

Alma Linux 8, 9

Debian 11, 12

Oracle Linux 8, 9

RHEL 8, 9

Rocky 8, 9

Suse 15

Ubuntu 20 LTS

GER-2293 - The SSHD timeout calculation fix was cherry picked into the GerritMS 3.7.1 release

GER-3211 - Customers will need to obtain and install a new version of the Git MultiSite "talkback" utility from Cirata support

JDK 11

Alma Linux 8, 9

Debian 11, 12

Oracle Linux 8, 9

RHEL 8, 9

Rocky 8, 9

Suse 15

Ubuntu 20 LTS

GER-2024 - Vanilla Gerrit documentation uses "replica" in the context of a read-only secondary. Cirata GitMS documentation uses the "replica" to mean full read-write primary. Be aware that the context of "replica" will very much determine its characteristics.

GER-2051 - Gerrit "experimental features" are not supported in GerritMS 3.7.0. Please contact support if more information is required.

GER-2054 - Plugin "webhooks" must only be deployed on a single node (or duplication of notifications will result).

GER-2124 - Command line tools that should not be run without consulting support: DeleteZombieDrafts, ChangeExternalIdCaseSensitivity, SwitchSecureStore, LocalUsernamesToLowercase.

GER-2137 - In rare circumstances a lack of quorum will appear as an internal server error to the git client making the change request.

NV-9418 - GitMS Talkback utility in 1.11.0 will not obtain Gerrit information if Gerrit is running Java 11.

NV-9465 - License properties are required in application.properties for Gerrit 3.7.0 licensing. See GitMS 1.11 Release notes, known issues

GER-2144 - Gerrit 3.7.6 accounts are only reactivated by account number. Need to set the user active with the account number, which can be retrieved in the output of the accounts endpoint.

GER-2241 - Some timezone settings on GerritMS servers (especially those that include switching to Daylight Savings) can result in an hour (or more) delay in updating Gerrit events, indexes, etc.

GER-2114 - GerritMS 3.7.0 is based on Gerrit 3.7.6+ there are additional fixes included. One of those was to fix CVE-2023-48795

GER-2133 - New property gerrit.replicated.cache.names.to.ignore has been added to allow control of default ignored caches. See Replicated cache names to ignore.

GER-2017 - The 3.7 release of Gerrit requires that "jgit" configuration items be moved into the ${site}/etc/jgit.config file. If you were running earlier version(s) of Gerrit you may have "jgit" configurations in "gerrit.config" or in the OS account that Gerrit runs as in the ~/.gitconfig configuration files. Gerrit default is for receive.autogc = false in order to prevent possible overwhelming of Java Object Heap Garbage Collection. Do not change this setting without consulting support.

GER-2119 - Gerrit has introduced a new feature which allows deadlines to be set on requests at either a server or client level. See Gerrit user-request-cancellation-and-deadlines It is strongly recommended to not use this feature. Such deadlines are necessarily longer in a fully primary/primary setup, especially when large latencies exist between servers. Use of this feature could cause non-atomic operations resulting in a half-finished state requiring manual administrative cleanup.

GER-2133 - GitMS "application.properties" property "gerrit.replicated.cache.names.to.ignore", by default includes the following caches.

lfs_locks,
jira_server_project,
its_rules_project,
change_notes,
default_preferences,
pure_revert,
groups_external_persisted,
groups_byuuid_persisted,
persisted_projects,
git_tags,
oauth_tokens

GER-2054 - Plugin "webhooks" must only be deployed on a single node (or duplication of notifications will result).