logo

WANDISCO GIT MULTISITE®
USER GUIDE

Version 1.9.8.1 Build 44f1fa68 Released: 25 November 2021
Last updated: 16th September 2024

Release notes support the installation of the latest product version.

For additional information go to:

1. Latest Release details

Version: 1.9.8.1 Build: 44f1fa68
Release: 25 November 2021

This release provides only the changes required to deploy Gerrit MultiSite 1.9.8.

1.1. Fixed

  • NV-7752 - Fixed a bug causing intermittent lost Gerrit indexes.

1.2. Known Issue

  • If upgrading from a hotfixed version Git MultiSite 1.9.6, you must remove any/all "HOTFIX" jar files from the "/opt/wandisco/git-multisite/replicator" directory.

    For example:

    rm -f /opt/wandisco/git-multisite/replicator/git-ms-replicator-1.9.6.3-HOTFIXGER-1008.jar

1.3. Software versions required or supported

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 6.10

  • CentOS 7.6

  • SLES 11.4

  • SLES 12.4

    • 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.

Java updates: The latest updates of Java 8 include critical bug fixes and security updates, the latest update is strongly recommended. Due to Java bug 8177809, you must use JDK 8 update 302 (8u302) or later.

We don’t support GitMS 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 GitMS 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:

  • C-Git - 2.19.1 (WANdisco version)

Other software versions:

  • JGit version installed with GitMS - 4.5.5.201812240535-r_WDv2

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

2. Previous GitMS 1.9 releases

2.1. Release 1.9.6.3

Version: 1.9.6.3 Build: a6cd3666
Release: 12 June 2019

2.1.1. Fixed

  • NV-7359 - Critical bug in JGit that could cause repository data loss fixed.

  • NV-7392 - Fixed bug that prevented the "update-config" REST API from working properly on Java 8

  • NV-7406 - Fixed bug that prevented large some LFS implementations from working

  • NV-7408 - Stopped filling log files with "Object went to …​"

  • NV-7440 - Fixed "rp-git-update" to properly handle white-space within certain fields

2.2. Release 1.9.5.5

Version: 1.9.5.5 Build dd32d91e
Release: 10 January 2019

2.2.1. New

  • NV-6983/NV-7042/NV-7130 - Enabled SystemD configuration files for SLES 12, CentOS/RHEL 7.

  • NV-7051 - For GerritMS, the following versions of MariaDB are now required: 10.1.36 on SLES 11, 10.2.21 on SLES 12.

  • NV-7078 - Incorporated a fix for CVE-2018-17456.

  • NV-7124 - GitMS now requires the replicated version of Git 2.19.1.

  • NV-7141 - Included a mechanism to disable the fix for CVE-2018-17456. See Submodule Verification for more information.

2.2.2. Fixed

  • NV-7133 - Fixed a bug causing the initial startup after install to fail.

2.2.3. 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

  • SUSE 12.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 GitMS 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 GitMS 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:

  • C-Git - 2.19.1 (WANdisco version)

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv4

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

2.3. Release 1.9.4.1

Version: 1.9.4.1 Build e10f07f0
Release: 22 October 2018

2.3.1. New

  • NV-6796 - New Git repos will always be deployed in GRO with the final state transitioning it out of GRO.

  • NV-6844 - GitMS will now always log either an ACCEPTED or DENIED on all AuthZ requests.

  • NV-6873 - Updated to use C language Git version 2.17.1.

  • NV-6919 - A clarification message has been added to the on Consistency Check UI when overlapping runs cause inconclusive/mismatched results.

  • NV-6924 - CRITICAL: AuthZ file is now parsed on product startup (instead of waiting until 1st change) thereby providing proper checking (it had been denying every request until the AuthZ file changed.

  • NV-6927 - The configurable max time to wait for Consistency Check to complete can now be enabled. See the Consistency check timeouts section for more information.

  • NV-6953 - Upgrade to use JGit version **.

  • NV-6963 - Enable alternate path to git gc command used during replicated garbage collection. See Command line JGit GC for more information.

  • NV-6976 - GitMS can poll GerritMS for account information and import information into GitMS.

  • NV-6990 - Downgraded all AuthZ requests to INFO level to prevent Dashboard spamming.

  • NV-6998 - GitMS installation now depends on the "net-tools" package. A future release will eliminate this dependency.

2.3.2. Fixed

  • NV-6471 - Prevented "comment size overflow" for JGit.

  • NV-6647 - Prevented PANIC during consecutive sync start/sync stops in a rare case.

  • NV-6709 - Properly remove the "git-multisite-hook" package when removing "git-multisite".

  • NV-6812 - PANIC prevented if adding a new repository to an replication group that the local node is not a member of.

2.3.3. Known Issues

  • NV-6988 - There is a required change to the log configuration file in this release. If you are upgrading to GitMS 1.9.4, and the logging configuration was modified in the previous version, then after upgrade has completed you will see the following warning:

    IMPORTANT: For gitms release 1.9.4, please ensure that you add the following to the log4j.properties file before restarting gitms. This additional log configuration stops spamming of the gitms.log file:

# CryptoFactory
log4j.logger.com.wandisco.security.crypto=INFO
# jsonpath
log4j.logger.com.jayway.jsonpath=INFO

    You need to add this property to to the log4j.properties file before restarting GitMS.

  • NV-6984 - Logging configuration warnings during upgrade
    There are changes to logging configuration files so if you are upgrading GitMS you will need to copy the new template configuration files into place after making sure that any local customizations have been preserved (in most cases there will be no local customizations).

    If you see the following message during upgrade then you need to determine if any changes were made to the configuration file. The message may be buried in installer output, the Linux "script" command can be used to help with searching. These changes then need to be added to the new configuration file and it copied into place.

    WARNING: Custom changes to logging configuration have been detected. The previous logging configuration
has been left in place. Please merge the changes from the latest version into your local configuration

    It is possible that changes were not made as our code does have the potential for false positives. This is something we will fix in a future release.

Please turn off thread dumps unless asked to enable them by WANdisco support. To do this edit the application.properties file and set threaddump.enabled=false.

2.3.4. 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.

  • JDK 7

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

We don’t support GitMS 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 GitMS 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:

  • C-Git - 2.17.1 (WANdisco version)

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv3

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

2.4. Release 1.9.3.3

Version: 1.9.3.3 Build d3b85284
Release: 2nd March 2018

2.4.1. New

  • NV-6650 - The talkback.sh script now supports invocation via the full path.

  • NV-6682 - It is now checked during upgrade that GITMS_UMASK is defined in main.conf, if not then upgrade will fail.

    Check GITMS_UMASK before upgrade

    Before upgrading you must check that GITMS_UMASK is set in the main.conf file on all machines. E.g.

    GITMS_UMASK=0022

    The value is normally 0000, 0002 or 0022, it is what you would want to use for a 'umask'. Before choosing a number, consider the current repository permissions and the desired level of security.

    Note: The account that GitMS runs as must be the account that owns every file system object in the repositories (including any directory in which the repositories reside).

  • NV-6712 - GFR RPM will now install into a symlinked installation directory.

  • NV-6752, NV-6783 - An autosftp script has been added to help upload talkbacks to the WANdisco support site. For more information see Uploading talkback files.

2.4.2. Fixed

  • NV-5948 - Eliminated duplicate warning messages on the dashboard for certain failed repository creation operations.

  • NV-6420 - The GitMS AuthZ parser now runs only once per AuthZ file update.

  • NV-6755 - Incorrect dashboard messages during repository moves from one replication group to another have been eliminated.

  • NV-6771, NV-6781, NV-6782 - Fixed the repository deployment process to eliminate race conditions. We advise that consistency checks are run (after upgrade) once per repository to find any damage caused by this bug. Please contact WANdisco support if any issues are found.

  • NV-6798, NV-6799 - Fixed many bugs impacting the performance of UI.

2.4.3. Known Issues

Please turn off thread dumps unless asked to enable them by WANdisco support. To do this edit the application.properties file and set threaddump.enabled=false.
If using one of the newer RHEL/CentOS 7.x platforms, you will need to run yum install net-tools before running the installer. The installation will fail without this.

  • NV-6848 - If you are upgrading using the tarball installer then "WRITE" permissions may need to temporarily be added to any files being upgraded. If a permission error is displayed then add the 'w'-bit (e.g. chmod a+w file1 file2 …​) and re-run the installation.

2.4.4. 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 GitMS 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 GitMS 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:

  • C-Git - 2.14.1

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv3

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

2.5. Release 1.9.2.3

Version: 1.9.2.3 Build e03f180a
Release: 17th October 2017

2.5.1. Fixed

  • NV-6686 - Fixed a critical GitMS bug preventing Gerrit reindexing.

NV-6471 change reverted
We had to revert the change needed to prevent commits with comments larger than JGit can handle. This bug will be fixed in a later release. In the meantime, please be careful not to commit with comments larger than 5MiB.

2.5.2. 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 GitMS 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 GitMS 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:

  • C-Git - 2.14.1

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv2

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

2.6. Release 1.9.1.1

Version: 1.9.1.1 Build dbb6359c
Release: 26th September 2017

2.6.1. New

  • NV-6025, NV-6612 - Updated C Git implementation to 2.14.1

  • NV-6051 - The Gerrit Delete Project plugin is now supported if using GitMS with Gerrit (GerritMS).

  • NV-6532 - Switched to using the Java G1 garbage collector.

2.6.2. Fixed

  • NV-5924 - You can no longer click the Complete Repair Process button before the repair process has started.

  • NV-6087 - There is now better logging for specific SSL configuration mistakes.

  • NV-6448 - The Flume Installation is now prevented from deleting the wrong data.

  • NV-6471 - An error message is now returned when a commit message exceeds the JGit limitation.

  • NV-6472 - A rare PANIC during node induction has been eliminated.

  • NV-6521 - The removal of online nodes is now prevented.

  • NV-6648 - DConE is prevented from trying to communicate with removed node endpoints.

2.6.3. Known Issues

  • NV-6604 - If you want to run GitMS with a specific umask you should edit the /opt/wandisco/git-multisite/config/main.conf file and set the variable GITMS_UMASK to your desired value (default is 0022).
    If you alter umask in the application.properties file then any changes will be lost on upgrade.
    Note - if there are "" around the values in the main.conf file then remove them.

    Essential for upgrades from GitMS 1.6.0.1
    If you are upgrading from GitMS 1.6.0.1 you must set a GITMS_UMASK value before upgrade (NV-6678).

2.6.4. 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 GitMS 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 GitMS 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:

  • C-Git - 2.14.1

Other software versions:

  • JGit version installed with GitMS - 4.5.2.201704071617-r_WDv2

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

2.7. Release 1.9.0.3

Version: 1.9.0.3 Build 21f6a437
Release: 4th May 2017

2.7.1. New

  • NV-5123 - Unattended installation is now documented, including all required environment variables.

  • NV-5346 - Documented the property setting needed to specify when to send license warnings.

  • NV-5539 - There is now wildcard support for branch and tag reference authorizations.

  • NV-5715 - The need to change "TasksMax" for Linux systems with systemd implementations is now documented.

  • NV-5888 - Authorization settings for controlling merge and NFF pushes have been added.

  • NV-5976 - Authorization based on "Account-Specific Branch Access" model (similar to gitolite) has been added.

  • NV-5993 - Encrypted passwords are enabled in Flume Sender config files (also NV-6164).

  • NV-6011 - Created a new REST endpoint to enable changing logging settings on the fly.

  • NV-6019 - GitMS is now supported to run with Java 8.

  • NV-6029 - The race condition free process for removing repositories from replication/service has been documented.

  • NV-6058 - Logging settings can now be changed though the UI on the fly and/or permanently.

  • NV-6129 - The UI will now grey out the Sync Stop button if any node is offline.

  • NV-6154 - The GitMS documentation has been converted to Asciidoctor - hope you like the new format!

  • NV-6183 - TLS mutual authentication is now supported for bi-directional communication connections.

  • NV-6223 - The list of email template variables for use during notifications has been documented.

  • NV-6236 - The GitMS UI will now display the state of the "Deny Non-Fast-Forward" setting for each repository and enable its modification.

  • NV-6303 - The repositories page no longer allows you to sort on "Last Modified" due to scalability issues.

2.7.2. Fixed

  • NV-4030 - Reference to the unused delegate.port in the application.properties file has been removed.

  • NV-4570 - Unnecessary warnings during node addition to a replication group have been eliminated.

  • NV-4930 - Pending replication groups now show even if a node is down during creation.

  • NV-5028 - A growl message now shown if the message body is empty in an e-mail template.

  • NV-5323 - Fixed replicator panic during induction when under load.

  • NV-5902 - You can no longer add a new node as Voter Only to an existing replication group. This is to prevent a panic.

  • NV-5913 - Fixed an issue that could cause a replicator to continuously try to remove a repository.

  • NV-5944 - GitMS will no longer remove repositories from the server without archiving first.

  • NV-5963 - Attempts to remove the Git master branch will be prevented.

  • NV-5979 - APIs are prevented from accepting references that begin with a '/' (this was causing divergence).

  • NV-5995 - ACP confusion prevented by returning inappropriate data during repository poll.

  • NV-6093 - The Replication Group sort header is fixed to say "Replication Group Name".

  • NV-6107 - Enabled the post-installation setup/maintenance of SSL by adding wd_cryptPassword.jar.

  • NV-6114 - Fixed the display of long notification template names in the UI.

  • NV-6171 - The deletion of a notification template if it is in use is prevented.

  • NV-6208 - The list of Git references is prevented from being printed into the logs.

  • NV-6224 - Fixed a rare bug that prevented the Sync Stop operation (also NV-6245).

  • NV-6258 - Fixed REST API endpoints to return 401 for authentication requests (not 405).

  • NV-6267 - Fixed a bug that caused a replication group to be sidelined inappropriately.

  • NV-6291 - Fixed the display of Perpetual licenses to properly display Perpetual.

  • NV-6292 - Fixed a number of scalability/performance bugs when large numbers of repositories are present.

  • NV-6302 - Fixed "PartialResultException" when LDAP provider is Active Directory.

  • NV-6323 - Fixed a rare bug that prevented the proper deployment of Gerrit .

  • NV-6338 - Fixed rare race condition exacerbated by bad networking that required an unnecessary replicator restart.

  • NV-6369 - The priority of the log message has dropped when REST API is used and bad path specification for repository is given.

2.7.3. Known Issues

  • NV-6108 - After an IP change the restart of a node can sometimes be significantly delayed. To avoid this the node can be manually restarted.

  • NV-6426 - If you remove a node which had an untrusted SSL certificate then a pending task will appear on the dashboard of the node that was used to remove it, even though the Nodes page shows it as removed.

  • NV-6604 - If you want to run GitMS with a specific umask you should edit the /opt/wandisco/git-multisite/config/main.conf file and set the variable GITMS_UMASK to your desired value (default is 0022).
    If you alter umask in the application.properties file then any changes will be lost on upgrade.
    Note - if there are "" around the values in the main.conf file then remove them.

    Essential for upgrades from GitMS 1.6.0.1
    If you are upgrading from GitMS 1.6.0.1 you must set a GITMS_UMASK value before upgrade (NV-6678).

2.7.4. 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 GitMS 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 GitMS 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:

  • C-Git - 2.12.0

Other software versions:

  • JGit version installed with GitMS - 4.5.0.201609210915-r_WDv1

Browser compatibility:

The following browsers are used in testing:

  • Firefox 36 or later

  • Google Chrome 56 or later

The latest versions of these browsers can also be used:

  • Internet Explorer

  • Safari

  • Opera

3. Earlier product versions

For Release Notes and documentation for earlier versions of Git MultiSite, see GitMS 1.7 Release Notes