Investigate whether the CNG auto-deploy process could also be repurposed for the reviews apps
As an item coming out of this retro: gitlab-org/quality/engineering-productivity/team#38 (closed)
Context
The gitlab-org/gitlab review apps currently run their rails code using the master CNG branch, but last stable tagged charts
This can lead to issues when the rail codebase depends on new chart changes. While switching to charts master would likely partially solve this. A better solution would be to be able to pin to the lastest successful builds from master to help protect the review apps from broken masters in CNG or charts.
One thing that already exists is the auto-deploy tags and branches. Using these would allow the review apps to use the latest charts and CNG version deployed to gitlab.com by default. Which would help ensure they are using recent but working versions.
Action Item
Investigate whether it is feasible to also push the auto-deploy tags to .com rather than just dev
The drawback is that these currently only exist on Dev. Partially to reduce bloat of tags and branches on gitlab.com, and partially because they sometime contain security changes before they are released.
We need to investigate whether the non-security ones could easily be pushed to .com during their tagging, and how easy it would be to potentially do that in a mirror on .com (we already have one for CNG), in order contineu to keep the auto-deploy branches and tags out of the main repo. (Because there are so many of them, that they make it harder for end-users to fine the real release tags for them)