we need a permanent always on (or frequently on on schedule) offline environment for testing

Problem to solve

Today we support 3 full versions of our code, and offline configurations.

We do not today have a constant offline environment to regression test each release of the self-managed software of at least the most recent released version, this could greatly upset our users who are ultimate and traditionally larger deals.

In some circumstances, we need to reproduce a bug in an earlier version.

This is currently difficult and manual to do.

Proposal

We should create one permanent offline environment which is for automated testing each monthly release - perhaps it runs the tests once a week when the SaaS updates are available to prevent regressions.

We should also empower support and development to have a simple script to be able to spin up an offline environment of a specific version to use for bug recreation and backport patch fixes as needed.

these environments will cost money but are worthwhile

perhaps they could be turned off (but kept with their data?) between uses of the perminant to save money if that saves money

and the temporary non current versions should alert/inform/remind people weekly they are on and there should be an easy way to decomission them when 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.