Geo validation tests

The Geo team performs manual testing and validation on common deployment configurations to ensure that Geo works when upgrading between minor GitLab versions and major PostgreSQL database versions.

This section contains a journal of recent validation tests and links to the relevant issues.

GitLab upgrades

The following are GitLab upgrade validation tests we performed.

February 2020

Upgrade Geo multi-server installation:

  • Description: Tested upgrading from GitLab 12.7.5 to the latest GitLab 12.8 package in a multi-server configuration.
  • Outcome: Partial success because we did not run the looping pipeline during the demo to monitor downtime.

January 2020

Upgrade Geo multi-server installation:

Upgrade Geo multi-server installation:

Upgrade Geo multi-server installation:

October 2019

Upgrade Geo multi-server installation:

  • Description: Tested upgrading from GitLab 12.3.5 to GitLab 12.4.1 in a multi-server configuration.
  • Outcome: Upgrade test was successful.

Upgrade Geo multi-server installation:

  • Description: Tested upgrading from GitLab 12.2.8 to GitLab 12.3.5.
  • Outcome: Upgrade test was successful.

Upgrade Geo multi-server installation:

  • Description: Tested upgrading from GitLab 12.1.9 to GitLab 12.2.8.
  • Outcome: Partial success due to possible misconfiguration issues.

PostgreSQL upgrades

The following are PostgreSQL upgrade validation tests we performed.

April 2020

PostgreSQL 11 upgrade procedure for Geo installations:

Verify Geo installation with PostgreSQL 11:

  • Description: Prior to making PostgreSQL 11 the default version of PostgreSQL in GitLab 12.10, we tested fresh installations of GitLab 12.9 with Geo installed with PostgreSQL 11.
  • Outcome: Installation test was successful.

September 2019

Test and validate PostgreSQL 10.0 upgrade for Geo: