logo

WANDISCO GERRIT MULTISITE®
USER GUIDE

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

WANdisco constantly monitors the possible impact of common vulnerabilities and exposures on all its products. See the WANdisco Community website for the latest ALM Product CVE Statements.

Release 1.10.1

Gerrit MultiSite 1.10.1 provides fixes for a number of issues found in the previous release. For deployment requirements, see the notes for the major release.

Version: 1.10.1 (v2.16.27-RP-1.10.1.1)
Release: May 20 2021

Fixes

  • GER-1404 - Enable delete-project plugin to work with projects in single node replication groups

  • GER-1499 - Fix delete-project plugin to properly archive projects

  • GER-1501 - Fix lfs plugin failure reporting

  • GER-1532 - Change talkback to use Gerrit SSH credentials for data collection purposes

  • GER-1549 - Fix delete-project plugin

  • GER-1553 - Determine how to enable the Gerrit replication plugin - Please contact WANdisco support before use.

  • GER-1562 - The replicated version of the delete-project plugin will ignore the "enablePreserveOption = false" setting

  • GER-1566 - Merge in Gerrit 2.16.27 release

  • GER-1606 - Enable removal of GerritMS leaving behind only vanilla Gerrit artifacts

  • GER-1607 - Fix lfs plugin to honor default storage location specification

  • GER-1625 - Fix show-replicator-stats command

  • GER-1628 - Periodically cleanup Gerrit pack file cache to enable proper file system release of deleted file space

  • GER-1629 - Fix gerrit-rp SystemD unit file to properly set critical task and file settings

Known Issue

  • GER-1292 - While the Delete project plugin works in the PolyGerrit UI, the following error appears in the old Gerrit UI: Code Review - Error, Plugin "delete-project" failed to load. In GerritMS 1.10.x, you must use PolyGerrit UI to interact with the Delete project plugin.

Required software versions:

  • GerritMS version: 1.10.1

  • Gerrit version: 2.16.27_WDv1

  • JGit version: 5.1.15-WDv1

  • C-Git is still 2.19.1

Module versions

  • ContentDistribution Version: 2.1.0

  • file-replication-service Version: 1.10.2.1

  • fusion-kernel Version: 2.1.0

  • fusion-kernel-slf4j-logging Version: 1.1.0

  • fusion-platform Version: 2.1.0

  • gerrit-gitms-interface Version: 1.1.1.1

  • git-ms-replicator Version: 1.10.1.1 Build: de3f8378

  • keystore-passwd-util Version: 1.2.11

  • Local UI Version: 1.10.1.1-GITMS Build: 0bc19738

  • notification-framework-core Version: 1.8.2.1

  • notification-framework-email Version: 1.8.2.1

  • security-framework Version: 2.0.2.1

  • vcs-common Version: 1.10.2.1

Available Plugins

  • Gerrit v2.16.27-RP-1.10.1.1

  • CodeMirror Editor v3.1.15

  • Commit-Message-Length-Validator v3.4.0

  • Delete-project v2.16.27-RP-1.10.1.1

  • Download-commands v2.16.27

  • Hooks v2.16.27

  • LFS v2.16.27-RP-1.10.1.1

  • Replication v2.16.27

  • Reviewnotes v2.16.27

  • Singleusergroup v2.16.27

Previous GerritMS releases

Release 1.10.0

Version: 1.10.0. Build: 0171
Release: February 4 2021

OS Support

The tested versions are listed below, we support these and higher patch levels. While we make every attempt to continue to support older Linux patch levels, it is sometimes not possible. In addition, because we do not test every patch level we may not know about an incompatibility that exists. For absolute compatibility it is best to choose the tested patch level.

  • CentOS 7 only

    CentOS/RHEL 6 operating systems are no longer supported.
    RHEL 8 and SLES 15 will be supported in a future release.

Java

  • JDK 8

Architecture

  • 64-bit only
    GerritMS is unable to support 32-bit architecture because this would impose crippling limits on scalability.

During install you are asked which user and group you want to use to run GerritMS. On Ubuntu this change does not apply system-wide, so some files have the default group set. This is not a problem, but something to consider when deciding on your OS.

Required software versions:

  • Git MultiSite - 1.10.

  • Databases: NoteDB/H2

  • Gerrit version 2.16.21-RP-1.10.0.1

  • C-Git - 2.19.1

Other software versions:

  • JGit version installed with GerritMS - 5.1.13-WDv1

Module versions

  • ContentDistribution Version: 2.0.0

  • file-replication-service Version: 1.10.1.1

  • fusion-kernel Version: 2.0.0

  • fusion-kernel-slf4j-logging Version: 1.0.1

  • fusion-platform Version: 2.0.0

  • gerrit-gitms-interface Version: 1.1.0.1

  • git-ms-replicator Version: 1.10.0.1 Build: 88a42bfb2ea94618b311d1ac7488e12d22ecd2e6

  • keystore-passwd-util Version: 1.2.5

  • Local UI Version: 1.10.0.1-GITMS Build:6ecd59a88eb04b30e19e5d9703d79512a05d0bf7

  • notification-framework-core Version: 1.8.1.2

  • notification-framework-email Version: 1.8.1.2

  • security-framework Version: 2.0.1.2

  • vcs-common Version: 1.10.1.1

Available plugins:

  • codemirror-editor version v3.1.12

  • commit-message-length-validator version v3.3.2

  • delete-project version v2.16.21-RP-1.10.0.1 (Not compatible with GerritMS 1.10.0)

  • download-commands version v3.0.16

  • hooks version v3.0.16

  • lfs version v2.16.21-RP-1.10.0.1

  • replication version v2.16.22 (Not compatible with GerritMS 1.10.0)

  • reviewnotes version v3.0.16

  • singleusergroup version v3.0.16

New Feature

Disable Replication
This new functionality lets you start Gerrit MultiSite in a non-replicated environment. See Disable Replication.

Fixes

  • GER-389 GerritMS/GitMS 1.10.0 fully support Git Atomic Commits

  • GER-540 PolyGerrit UI support added to WANdisco replicated Gerrit LFS

  • GER-541 Gerrit 2.16.21 supported by GerritMS 1.10.0

  • GER-687 Offline reindexing performance improved

  • GER-742, GER-794 Content Delivery cleaned up of stale files in rare circumstances

  • GER-813 Only Java 8 supported in this release (OpenJDK, Oracle)

  • GER-830 Better documentation of non-interactive install requirements

  • GER-833 Gerrit UI and Gerrit Logs now agree on specific failure issues

  • GER-862 GerritMS/GitMS 1.10.0 only support Gerrit 2.16.21 post ReviewDB to NoteDB migration

  • GER-873 Permissions of files created during installation now properly adhere to specified umask

  • GER-936 Retraction of "Distinct Events" implementation - no longer supported

  • GER-963 Gerrit "Replication Plugin" not supported

  • GER-967 Account Inactivation State now properly replicated

  • GER-976 Small Paxos proposals no longer require Content Delivery

  • GER-1021 Fixed extremely rare race condition that could cause partial update in a repository

  • GER-1026 Fixed ability to unstar a starred change

  • GER-1048 Persisted events are now cleaned up

  • GER-1418 Performance enhancement to pack file opening

Known Issues

  • GER-1522: Multiple users simultaneously committing to same repository may cause a block on ref updates. There is currently a risk that Gerrit will timeout before the issue clears itself. If timeouts become a problem, change the following property, increasing it incrementally until the timeouts stop.

    1. Open the <gerrit.home>/etc/gerrit.config file in an editor.

    2. Ensure the following property and corresponding value is in place.

      [noteDb]
      sequenceRetryMaxTimeoutSecs = 30

      Note that by default this maximum timeout is 30 seconds. Increase the timeout by 5 or 10 seconds, then retest. Repeat the change until timeouts stop happening.

    3. Save and restart Gerrit service.

Alternatively, you can make the change via the command line, using the following command:

git config -f path/to/gerrit.config noteDb.sequenceRetryMaxTimeoutSecs 35

This example sets the maximum timeout at 35 seconds.

  • GER-1500: The WANdisco enhanced Delete-project plugin has found not to work properly in Gerrit MS 1.10.0
    Do not install or use the Delete-project plugin in this initial 1.10 release. It will be fixed in the next release.

  • GER-1404: single node replication groups fail to delete gerrit projects.

    • Workaround: Do not use single node replication groups during testing.

    • Status: To be fixed in next release.

  • GER-1053: Replicated LFS locking is not supported in the first 1.10 release.

    • Workaround: None.

    • Status: Support to be added in a future release.

  • GER-474: JGit 4.6.0 and later must have "autogc" set to false.

    • Notes: When running GerritMS 1.10, every modification made to a GerritMS repository may trigger a Git GC. This could negatively impact performance when running with large repositories, where frequent GC operations could cause a minute or more of delay.

      Recommendation: Turn this feature off and periodically use GitMS for repository garbage collection.
      See Disable auto-GC with the following command for the required step.

Evaluate Repository Garbage Collection requirements

Gerrit 2.16 init automatically triggers reindexing

Running a Gerrit init (java -jar gerrit.war init) will automatically result in a re-indexing projects. Before running Gerrit init, ensure that you measure the impact of a reindexing. If applicable, add the following flag to block the reindex:

java -jar gerrit.war init --no-reindex
--no-reindex

Don’t automatically reindex any entities (default: false)

Gerrit 2.15/2.16 Strict label validation

From Gerrit 2.15, posting a review including a vote on any labels that do not exist or are outside of the permitted range based on the ACLs can now result in a failure of the entire operation. This feature is currently set to "off" by default.

To enable Strict label validation:

  1. Open the gerrit.config file.

  2. Ensure the following parameter and value are included.

    [change]
              strictLabels = true
  3. Save the file. Restart Gerrit to apply the change to the node.

    Make the edit on a node by node basis as each node handles and enforces the request individually.

Release 1.9.7

Version: 1.9.7. Build: 0018
Release: 15 October 2019

This is a full release of Gerrit MultiSite enables customers to run Gerrit 2.13.12 with Chrome 76 changes. It will supersede all prior GerritMS releases and only includes critical fixes.

Fixed

  • GER-870 - Fixes required in order to operate properly with Chrome 76.

  • GER-877 - Fix Gerrit index event propagation for All-Users repository changes.

  • GER-885 - Back out temporary fixes to enable hotfix for LFS Plugin (which removed the UI portion).

If you are running GerritMS 1.9.6, you may use an expedited installation procedure. For more information, please contact WANdisco Support.

Known issue

  • GER-1753 - There is a broken link on the table of contents for the Gerrit documentation hosted with Gerrit MultiSite’s installation of Gerrit. The Default Android Workflow link should go to https://source.android.com/setup/develop. This issue is fixed in later versions.

Version: 1.9.6 Build 0009 ( 2.13.12-RP-1.9.6.1)
Release: 12 June 2019

Fixed

  • GER-829 - Critical bug in JGit that could cause repository data loss fixed.

Known Issues

  • GER-834 Important note if running Gerrit 2.13.11 on SLES 11.3 - See details.

Software versions required or supported

The tested versions are listed below, we support these and higher patch levels:

  • CentOS 6.10

  • CentOS 7.6

  • SLES 11.4

    • Contact WANdisco Support for more information about running on this platform.

  • SLES 12.4

  • JDK 7

    • JDK 8 is only tested with CentOS currently but is supported on all platforms.

We don’t support GerritMS on 32-bit architecture because this would impose serious limits on scalability. You must deploy on a 64-bit OS.

Required software versions:

  • Git MultiSite - 1.9.6

  • Databases:

    Operating System Version Tested

    CentOS 6

    Percona 5.6.43

    CentOS 7

    Percona 5.6.43

    SLES 11

    MariaDB 10.1.36

    SLES 12

    MariaDB 10.2.24

  • Vanilla Gerrit - 2.13.12

  • C-Git - 2.19.1

Other software versions:

  • JGit version installed with GerritMS - 4.5.5.201812240535-r_WDv1

Release 1.9.5.1

Version: 1.9.5.1 Build 0007 (2.13.12-RP-1.9.5.1)
Release: 25 January 2019

IMPORTANT: Do not use Gerrit’s internal repository garbage collection mechanism with Gerrit MultiSite 1.9.5.1 or earlier. A serious JGit bug (GER-829) was fixed in Gerrit MS 1.9.6. See Garbage Collection.

New

  • GER-821 - Critical Security Patch: Support for Gerrit 2.13.12.

Delete Projects Plugin
The Delete Projects Plugin in this release is version 2.13.11. This is compatible with Gerrit 2.13.12.

Known Issues

  • GER-834 Important note if running Gerrit 2.13.11 on SLES 11.3 - See details.

Software versions required or supported

The tested versions are listed below, we support these and higher patch levels:

  • RHEL 6.6

    • Red Hat 6 requires the RHEL Server Optional repository to be enabled in Red Hat Network.

  • CentOS 6.9

    • See Red Hat note above.

  • RHEL 7.1

  • CentOS 7.5

  • SUSE 11.4

    • Contact WANdisco Support for more information about running on this platform.

  • SLES 12 SP3

    • SP3 is the minimum version required.

  • JDK 7

    • JDK 8 is only tested with CentOS currently but is supported on all platforms.

We don’t support GerritMS on 32-bit architecture because this would impose serious limits on scalability. You must deploy on a 64-bit OS.

During install you are asked which user and group you want to run GerritMS as. On Ubuntu this change does not apply system-wide, so some files have the default group set. This is not a problem, but something to consider when deciding on your OS.

Required software versions:

  • Git MultiSite - 1.9.5

  • Databases:

    Operating System Version Tested

    CentOS 6

    Percona 5.6.42

    CentOS 7

    Percona 5.6.42

    SLES 11

    MariaDB 10.1.36

    SLES 12 SP3

    MariaDB 10.2.21

  • Vanilla Gerrit - 2.13.12

  • C-Git - 2.19.1

Other software versions:

  • JGit version installed with GerritMS - 4.5.5.201812240535-r_WDv1

Release 1.9.4.1

Version: 1.9.4.1 Build 0082 (2.13.11-RP-1.9.4.1)
Release: 22 October 2018

IMPORTANT: Do not use Gerrit’s internal repository garbage collection mechanism with Gerrit MultiSite 1.9.5.1 or earlier. A serious JGit bug (GER-829) was fixed in Gerrit MS 1.9.6. See Garbage Collection.

New

  • GER-479 - Update GitMS with Gerrit account information to enable proper licensing checks.

  • GER-485/GER-539 - Major new feature -"Gerrit LFS plugin" so that LFS data is replicated to required nodes.

  • GER-604 - Enabled reindex.sh to work within the context of a reverse proxy frontend.

  • GER-608 - Support the Gerrit ITS-JIRA plugin. See Solution plugins for Gerrit for more information.

  • GER-615 - Support for Gerrit 2.13.11 patch set.

  • GER-621 - Better support for GerritMS in the talkback utility.

  • GER-651 - Backported a Gerrit 2.14 fix to prevent issues when an LDAP account has a null username field.

  • GER-674 - Backported a Gerrit fix to replace "Random" with "SecureRandom".

  • GER-686 - Enable support for Physically Nested Repositories via a non-default configuration setting. See documentation.

  • GER-693 - Enable Gerrit startup support for TLSV1.2 by default.

  • GER-695 - Added documentation to specify -Dhttps.protocols=TLSv1.2 as part of java command to run the init command during upgrade.

  • GER-696 - Added documentation on how to speed up Gerrit reindexing by using multiple threads.

  • GER-795 - Backported as much of CVE-2018-17456 as possible from latest the Gerrit releases.

Fixed

  • GER-382 - No longer echo typed passwords to the screen during runs of "sync_repos.sh".

  • GER-405/GER-632/GER-691 - Properly replicate accounts to remote nodes when they are created/modified.

  • GER-451 - Minimized the delay in updating "My Changes" on remote nodes after a change.

  • GER-468 - Proper computation of intervals between servers in different timezones.

  • GER-500 - Prevented removal of "top level" Git repo if it has physically nested repositories below it.

  • GER-520 - Fixed a bug in the Delete Project plugin where a down node would not remove a repository properly.

  • GER-614 - Installer in prevented from running as the wrong account.

Known issues

Maven Central no longer supports TLS v1.1
As Maven Central no longer supports TLS v1.1, if using Java 7 you will need to enable TLS v1.2 manually in order to use Gerrit re-init. See the Gerrit docs for more information - https://www.gerritcodereview.com/releases/2.13.md#HTTPS-TLS1_1-support-discontinued-by-Maven-Central. Java 8 supports TLS v1.2 by default and so is not affected.
Gerrit init required after installation
After the GerritMS installer is finished, perform a gerrit init. This is only needed for first time installations, not upgrades.
  • GER-740 Gerrit LFS will not work for a non-replicated repository. The work-around is to create a single-node replication group which contains the repository. This deficiency will be fixed in the next version of GerritMS.

  • GER-834 Important note if running Gerrit 2.13.11 on SLES 11.3
    If you are running Gerrit 2.13.11 on SLES 11.3, then you may encounter an issue that prevents Gerrit from starting up after a shutdown. This is because Gerrit uses start-stop-daemon to manage the process which happens to be incompatible with the SLES version of the start-stop-daemon).

    Workaround
    Ensure START_STOP_DAEMON=0 in gerrit.sh.

    # START_STOP_DAEMON
    #   If set to "0" disables using start-stop-daemon.  This may need to
    #   be set on SuSE systems.

Software versions required or supported

The tested versions are listed below, we support these and higher patch levels:

  • RHEL 6.6

    • Red Hat 6 requires the RHEL Server Optional repository to be enabled in Red Hat Network.

  • CentOS 6.9

    • See Red Hat note above.

  • RHEL 7.1

  • CentOS 7.5

  • SUSE 11.4

    • Contact WANdisco Support for more information about running on this platform.

  • SLES 12 SP3

    • SP3 is the minimum version required.

  • JDK 7

    • JDK 8 is only tested with CentOS currently but is supported on all platforms.

We don’t support GerritMS on 32-bit architecture because this would impose serious limits on scalability. You must deploy on a 64-bit OS.

During install you are asked which user and group you want to run GerritMS as. On Ubuntu this change does not apply system-wide, so some files have the default group set. This is not a problem, but something to consider when deciding on your OS.

Required software versions:

  • Git MultiSite - 1.9.4 or 1.9.5

  • Databases:

    If using GitMS 1.9.4:

    Operating System Version Tested

    CentOS 6

    Percona 5.6.41-84.1-56

    CentOS 7

    Percona 5.6.41-84.1-56

    SLES 11

    MariaDB 10.1.36

    SLES 12 SP3

    MariaDB 10.2.18

    If using GitMS 1.9.5:

    Operating System Version Tested

    CentOS 6

    Percona 5.6.42

    CentOS 7

    Percona 5.6.42

    SLES 11

    MariaDB 10.1.36

    SLES 12 SP3

    MariaDB 10.2.21

  • Vanilla Gerrit - 2.13.11

  • C-Git - 2.17.1 if using GitMS 1.9.4, 2.19.1 if using GitMS 1.9.5.

Other software versions:

  • JGit version installed with GerritMS - 4.5.2.201704071617-r_WDv4

Release 1.9.3.5

Version: 1.9.3.5 Build 0019 (2.13.9-RP-1.9.3.5)
Release: 4th April 2018

New

  • GER-589 - Percona 5.6 is now required for running GerritMS 1.9.3. Support for Percona 5.7 has been removed to prevent deadlock.

  • GER-584 - Enabled trading processor consumption against index and event replication delays via tunable properties.

  • GER-613 - Time Zone offset is now properly computed for all possible timezones (some Linux timezones are not possible due to JAVA issue).

Fixed

  • GER-498, GER-568 - sync_repo.sh enhanced to prevent attempts to add inappropriate repositories, better logging.

  • GER-551 - Fixed a bug preventing cloning of large repositories (fails at 30 second mark).

  • GER-555, GER-575, GER-582, GER-594 - Fixed bugs preventing proper Gerrit index and event replication.

  • GER-564, GER-567 - Fixed bugs preventing proper handling of JSON files in Gerrit event replication.

  • GER-570 - reindex.sh script fixed to handle proper index path creation in certain cases.

  • GER-573 - Fixed a bug where indexing could be delayed by 2 hours.

  • GER-620, GER-632, GER-646 - Fixed an indexing issue for newly created accounts.

Known issues

  • GER-562 - During the GitMS upgrade of a GitMS/GerritMS system the json files in the …​/gerrit/gerrit_events tree need to be removed. Remove them when GitMS is fully down. These files are internally formatted in a release dependent manner so could cause problems after the upgrade if they are not removed.

  • GER-628 - When using the Gerrit Delete Project plugin there will be 2 ignorable errors generated into the Gerrit error_log file on all of the nodes other than that where the clean up request was made.

  • GER-630 - CentOS/RHEL 7 and SLES 12: To avoid Gerrit Event and Indexing replication issues, use these instructions for setting your system timezone.

  • You must login to the Gerrit UI on a node before you can clone (or use REST API endpoints) from that node. This will be fixed in the next version of GerritMS.

  • GER-654 - In order to use OAuth with Gerrit you will need to use OAuth 2.13.6 and Java 8.

  • GER-656 - The gerrit#serverId configuration value must be the value it was first created with. This will be the same at all sites.

  • GER-665 - The Gerrit war file for some of the built-in plugins contains the tag 2.13.11 and not 2.13.9 as would be expected. For those plugins the 2.13.9 and 2.13.11 tags are on the same commit. Our build process simply chose the wrong tag to include. You will see this in the following instances:

    • In the UI under Plugins

    • In the backend API

    • When running the command option --list-plugin

Software versions required or supported

The tested versions are listed below, we support these and higher patch levels:

  • RHEL 6.6

    • Red Hat 6 requires the RHEL Server Optional repository to be enabled in Red Hat Network.

  • CentOS 6.6

    • See Red Hat note above.

  • RHEL 7.1

  • CentOS 7.1

  • SUSE 11.3

    • Contact WANdisco Support for more information about running on this platform.

  • JDK 7

    • JDK 8 is only tested with CentOS currently but is supported on all platforms.

We don’t support GerritMS on 32-bit architecture because this would impose serious limits on scalability. You must deploy on a 64-bit OS.

During install you are asked which user and group you want to run GerritMS as. On Ubuntu this change does not apply system-wide, so some files have the default group set. This is not a problem, but something to consider when deciding on your OS.

Required software versions:

  • Git MultiSite - 1.9.3

  • Percona XtraDB Cluster - 5.6.37-82.2-56

  • MariaDB:

    Operating System Version Tested

    CentOS 6

    Percona 5.6.37-82.2-56

    CentOS 7

    Percona 5.6.37-82.2-56

    SLES 11

    MariaDB 10.1.7

    SLES 12

    MariaDB 10.2.8

  • Vanilla Gerrit - 2.13.9

  • C-Git - 2.14.1

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv2

Release 1.9.2.2

Version: 1.9.2.2 Build 0008 (2.13.9-RP-1.9.2.2)
Release: 17th October 2017

Fixed

  • GER-536 - Fixed a bug that prevented reindexing of very rare commit types.

  • GER-552 - Cherry-picked a bugfix that enables the cloning of very large repos - see bugs.chromium.org for more information.

Known Issues

  • GER-554 - Before upgrading from a previous version you must set the following properties in the gerrit.config file:

    [cache "diff"]
        timeout = 15000
    [cache "diff_intraline"]
        timeout = 15000
  • GER-562 - During the GitMS upgrade of a GitMS/GerritMS system the json files in the …​/gerrit/gerrit_events tree need to be removed. Remove them when GitMS is fully down. These files are internally formatted in a release dependent manner so could cause problems after the upgrade if they are not removed.

  • GER-571 - If you want specific Gerrit features that had previously been used, then after upgrade you need to run the following:

    1. To display the download commands you need to enable the "download-commands" plugin ("Stable 2.13", see here). To do this run the command:

      java -jar /home/gitms/gerrit/bin/gerrit.war init -d /home/gitms/gerrit --install-plugin=download-commands
    2. To enable the server side Hooks (the Gerrit replacement to the Git hooks), you need to run the command:

      java -jar /home/gitms/gerrit/bin/gerrit.war init -d /home/gitms/gerrit --install-plugin=hooks
  • GER-572 - If using Gerrit with Percona then nodes may fail to start due to an error in the mysqld_safe script. For more information see the Percona website.
    A work around is to edit the mysqld_safe script with the following:

    1. Run the command vim /usr/bin/mysqld_safe. You will need to edit the line beginning if [ $ret, +/- line 220.

    2. Change from:

      if [ $ret > 0 ]; then

      to:

      if [ "$ret" -gt "0" ]; then

Software versions required or supported

The tested versions are listed below, we support these and higher patch levels:

  • RHEL 6.6

    • Red Hat 6 requires the RHEL Server Optional repository to be enabled in Red Hat Network.

  • CentOS 6.6

    • See Red Hat note above.

  • RHEL 7.1

  • CentOS 7.1

  • SUSE 11.3

    • Contact WANdisco Support for more information about running on this platform.

  • JDK 7

    • JDK 8 is only tested with CentOS currently but is supported on all platforms.

We don’t support GerritMS on 32-bit architecture because this would impose serious limits on scalability. You must deploy on a 64-bit OS.

During install you are asked which user and group you want to run GerritMS as. On Ubuntu this change does not apply system-wide, so some files have the default group set. This is not a problem, but something to consider when deciding on your OS.

Required software versions:

  • Git MultiSite - 1.9.2

  • Percona XtraDB Cluster - 5.6

    This version was originally shipped dependent on Percona 5.7, but due to issues found subsequent to shipment we have reverted the dependency to Percona 5.6.
  • MariaDB:

    Operating System Version Tested

    CentOS 6

    Percona 5.6

    CentOS 7

    Percona 5.6

    SLES 11

    MariaDB 10.1.7

    SLES 12

    MariaDB 10.2.8

  • Vanilla Gerrit - 2.13.9

  • C-Git - 2.14.1

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv2

Release 1.9.1.2

Version: 1.9.1.2 Build 0014
Release: 26th September 2017

New

  • GER-434 - During install, the administrator is now notified if environment variables that change "curl" behavior are set.

  • GER-439 - There is now full support for the Gerrit "Delete Project" Plugin. See Delete projects for more information.

  • GER-441 - GerritMS now supports Java 8.

  • GER-443 - You can now specify sub-second values for Gerrit Events replication properties. See Gerrit event stream for more information.

  • GER-492 - Gerrit 2.13.9 is now supported.

Fixed

  • GER-324 - Fixed a rare bug where repositories would take a long time to deploy.

  • GER-359 - Fixed a bug where a replicated change event would generate a MissingObjectException.

  • GER-429 - There are now better error message delivered to users whose push failed because of a prior push.

  • GER-432 - There are now better error message when repository deployment failed due to existing on-disk artifacts.

  • GER-468 - Fixed a bug where time differences between sites were incorrectly calculated during Daylight Savings Time periods for specific Time Zones.

Known Issues

  • GER-454 - For successful upgrade you need to remove any redundant slashes before upgrade is attempted. Redundant slashes include any duplication of slashes or a slash at the end of the string.
    The following steps need to be performed for any GerritMS repositories that have redundant slashes in their GitMS file path. The example uses the example repository All-Users.git:

    1. Remove the All-Users.git repository from GitMS

    2. Add the All-Users.git repository back into GitMS, this time without redundant slashes

    3. Edit the application.properties file and remove the redundant slashes from any path specified therein (especially, gerrit.root, gerrit.repo.home)

  • GER-512 - Before upgrading to a new version you need to edit the <gerrit.home>/etc/gerrit.config file to contain the following:

    [container]
            startupTimeout = 200

    This will enable a successful restart after upgrade.

  • GER-535 - The my.cnf needs to be changed due to a clash between Gerrit’s use of zeros for dates and in dates, and the SQL standard change to disallow such values. Specifically, the "sql-mode" must not have NO_ZERO_IN_DATE nor NO_ZERO_DATE. See the Percona XtraDB section for more information.

Software versions required

The tested versions are listed below, we support these and higher patch levels:

  • RHEL 6.6

    • Red Hat 6 requires the RHEL Server Optional repository to be enabled in Red Hat Network.

  • CentOS 6.6

    • See Red Hat note above.

  • RHEL 7.1

  • CentOS 7.1

  • SUSE 11.3

    • Contact WANdisco Support for more information about running on this platform.

  • JDK 7

    • JDK 8 is only tested with CentOS currently but is supported on all platforms.

We don’t support GerritMS on 32-bit architecture because this would impose serious limits on scalability. You must deploy on a 64-bit OS.

During install you are asked which user and group you want to run GerritMS as. On Ubuntu this change does not apply system-wide, so some files have the default group set. This is not a problem, but something to consider when deciding on your OS.

Required software versions:

  • Git MultiSite - 1.9.1

  • Percona XtraDB Cluster - 5.6

    This version was originally shipped dependent on Percona 5.7, but due to issues found subsequent to shipment we have reverted the dependency to Percona 5.6.
  • MariaDB:

    Operating System Version Tested

    CentOS 6

    Percona 5.6

    CentOS 7

    Percona 5.6

    SLES 11

    MariaDB 10.1.7

    SLES 12

    MariaDB 10.2.8

  • Vanilla Gerrit - 2.13.9

  • C-Git - 2.14.1

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv2

Earlier product versions

For Release Notes and documentation for earlier versions of Gerrit MultiSite, see GerritMS 1.7 Release Notes