logo

WANDISCO GIT MULTISITE®
USER GUIDE

Version 1.10.2 Build: 7906f912 Released: 9 February 2023
Last updated: 16th September 2024

Release notes support the installation of the latest product version.

For additional information go to:

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

Version: 1.10.2.4 Build: 7906f912
Release: 9 February 2023

This is a patch release fixes an issue where pack files could become excessively large.

  • GER-1824 - Minimize pack file size for replicating repository updates.

For deployment requirements, see the notes for the major release.

Version: 1.10.2.2 Build: 28d8ab9f
Release: 17 November 2022

This is a patch release is intended only for use with Access Control Plus (ACP) AuthZ policy enforcement, not Gerrit. The following fixes are included.

  • NV-9046 - Properly enable M+ privilege.

  • NV-9056 - properly implement default AuthZ policy.

Version: 1.10.2.1 Build: 1086e0da
Release: 3 March 2022

Git MultiSite 1.10.2 provides fixes for two issues found in the previous release. For deployment requirements, see the notes for the major release.

  • NV-8617 - Fixed an issue where content delivery could be mistakenly removed, requiring a time-consuming workaround that included loss of repository access for a short time and required a restart of all replicators in the containing replication group.

  • NV-8650 - Added a check that the pack files used to update the repository do not contain any corruption. Due to the graph nature of Git, sometimes these pack files can contain objects that the repository already has. If the repository is corrupt, then the pack files can be corrupt, and the update to the repository will fail.

    The code that does this check in GitMS 1.10.1 is flawed and may only catch the corruption on the nodes remote from the initial push (originating node). The repository on the remote nodes will go Local Read-only (LRO). We are fixing this flaw.

    The new code included in this release will ensure that the pack file makes health checks before creating the update proposal and will reject the update request at that time. This will prevent a slip into the LRO state. However, the real cause may very well be that the repository is already corrupt. You should run a “git fsck --full --strict” to validate that the repository is healthy (and it was the pack file(s) that were corrupt). Run that command on all nodes in the replica family and repair the other sites with an uncorrupt version. If all replicas are corrupt, then please contact WANdisco support.

Release 1.10.1

Version: 1.10.1.0 Build:de3f8378
Release: 20 May 2021

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

Fixed

  • NV-8003 - GitMS account licensing update protocol is now more efficient

  • NV-8178 - logrotation.ser file is now human readable

  • NV-8182 - Additional warnings when adding node to a replication group

  • NV-8201 - Fixed bug that could cause two emails to be sent for a single event

  • NV-8237 - Enable keystores with multiple keys

  • NV-8263 - Periodically cleanup JGit pack file cache to enable proper file system release of deleted file space

Release 1.10.0

Version: 1.10.0.0 Build:88a42bfb
Release: 4 February 2021

Git MultiSite 1.10.0.0 is exclusive for use with GerritMS 1.10.0.
Do not install or deploy if you are not also running GerritMS 1.10.0.

Fixed

  • NV-4185 - A consistency check is now run whenever a repository is deployed

  • NV-4229 - An attempt to browse to an invalid repository path is now an INFO

  • NV-5360 - Moving the scheduling-managing node is now done consistently across timezones

  • NV-5768 - Can now delete an incompletely created replication group

  • NV-6404 - Permissions for "not this team" and "not this user" are implemented when GitMS is configured to do AuthZ

  • NV-6534 - Flume SSL passwords are now stored encrypted

  • NV-6550 - Content Delivery is now cleaned up after unsidelining a repository

  • NV-6689 - Java 8 is now required

  • NV-6703 - Installation of GitMS can now be automated without a UI driver

  • NV-6751 - Disk space warnings now easier to understand

  • NV-6865 - The “CheckRepositoryResultSuccessProposal” event in notifications is now deprecated and will not trigger a notification email

  • NV-6890 - EULA acceptance is now done on WANdisco downloads page and has been removed from the product

  • NV-7006 - Removed nodes will no longer show up on "map" page

  • NV-7291 - New property to disable stack tracebacks from showing up in REST API output, see Enable/Disable Stack Traces

  • NV-7354 - Now able to remove repository from replication even if it has pending transactions

  • NV-7512 - UI for Replication Group node roles will now show correct roles

  • NV-7546 - Repository Repair UI is now more robust

  • NV-7555 - Proper error message now displayed when incorrect file system path specified during repository addition

  • NV-7563 - Proper error message now displayed when trying to add a repository with a duplicate name

  • NV-7603 - REST API Breaking change: <replicationgroup/> has been renamed to <replicationGroup/> in some APIs to match other APIs

  • NV-7615 - SUSE 11 / SLES 11 is no longer supported as a platform

  • NV-7698 - Fixed a bug causing talkback to infinite loop with eco-system > 3 nodes

  • NV-7715 - GitMS will now periodically check for proper replicated Git Binaries and log ERROR if fails

  • NV-7725 - The repository GC REST API invoked operation can now be tracked to completion (on all nodes) by following all returned tasks

  • NV-7752 - Intermittent missing Index event bug has been fixed

  • NV-7797 - Upgrade from prior GitMS version requires WD_SYSTEMD_TASKSMAX setting in "main.conf" file, see Check main.conf Configuration File

  • NV-7921 - Large proposals will now use Content Delivery automatically

  • NV-7951 - Content Delivery will now prevent CPU over-use and possible NODE_OFFLINE issues

  • NV-8037 - Proposals with small associated data will transfer data inline (not via Content Delivery)

  • NV-8166 - CentOS 6 is no longer a supported platform

Additional fixes

  • Many defects were fixed in the GitMS installer

  • Many defects were fixed in the talkback utility

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 7.6

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

  • JDK 8

    • Important: JDK 7 is no longer supported. You must now run JDK 8.

      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.

System user and group assignment for GitMS

During install you are asked which user and group you want to run GitMS as. The primary group of the user account that GitMS will be run as should ALWAYS be used as the group that GitMS should be run as or else there will be a mix of directory entries (directories, files) that contain either theAccount:theGroup or theAccount:thePrimaryGroup since the running process is most likely to run as theAccount:thePrimaryGroup and not theAccount:theGroup.

Required software versions:

  • C-Git - 2.19.1 (WANdisco version)

Other software versions:

  • JGit version installed with GitMS - 5.1.13-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

Earlier product versions

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