we need both a permanent openShift environment as well ways to spin up versioned testing environments that can live as long as needed

Problem to solve

Today we support 3 full versions of our code.

We advertise and partner to allow for OpenShift as a platform.

In many circumstances, we need to reproduce a bug in a current or earlier supported version of the software. We may then need to fix or backport and test this fix (it could be a security fix or a useability fix).

This is currently difficult and manual to do.

We also should be testing each SaaS release for regression issues to catch them before (and as a canary for) the versioned releases so customers aren't finding them. if we support it we should test and stand by it.

Proposal

we should work with quality to initiate a working group and a larger project to have a permanent OpenShift environment on the current release for all teams (a canary) and also a script that can generate a version of GitLab with a specific version and patch level by updating variables.

One (latest) environment should always be available to support and dev and testing (or perhaps we need 2) but should be kept off if that saves money when not actively running tests or in use.

The temp prior version environments should automatically add themselves to some mechanism to be watched and alert/remind people to spin the environment down after 1 week (possibly with scripts to automatically pause the environment off hours if that saves money?) and there should be a nice easy way to decommission the environment when the work is done.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

Is this a cross-stage feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.