Reorganize pre-release environment
We currently use pre.gitlab.com
as our testing environment for patch releases and release candidates for self-managed releases. This is necessary because we don't use the self-managed release package in our day-to-day environments, which allows us to have a final sanity check before releasing a package to the public.
With #638 (closed) being implemented, we now have workloads competing for an environment:
- Active self-managed patch release, such as 12.9.4
- Release candidate for the next version, such as 12.10.0-rc42
This creates an issue where patch releases for the active version can't be automatically deployed to pre
once an RC is out. This is not great because we have the need to deploy both and run QA on both of these environments.
I suggest we create two new environments:
Name | Purpose |
---|---|
rc.gitlab.* | Environment used for deploying release candidates. These packages are not officially used by users, but will become officially released packages. |
release.gitlab.* | Environment used for deloying packages that will be officially used by users. |
This would make pre.gitlab.com
unecessary, and @jarv suggested that we should move away from using gitlab.com
domain for these internal environments.