Skip to content

Do not test upgrades when SHA version is provided

Grzegorz Bizon requested to merge fix/gb/do-not-test-sha-version-specific-upgrades into master

Description

When we provide RELEASE variable to the pipeline trigger, which means that we want to test GitLab that has built using a specific SHA, which usually means that we are testing code from a merge request, it does not make sense to test upgrade process. To correctly test that, we would need to build a corresponding EE version, which is not available at the time we run tests.

Currently it appears that we ignore RELEASE in the test command anyway, and we are testing nightly CE -> nightly EE upgrade.

Proposal

Do not test CE -> EE upgrade for specific SHAs.

Merge request reports