ci: stop GitLab deploying previews and production before the switch #571
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amaurycoudr/chess-project!571
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/498-freeze-gitlab"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
GitLab's job list,
.gitlab-ci.ymland its includes:Helpers gone with them:
.review-rules,.image-rules,.registry-login,.skip-no-preview,DEPLOY_DOMAIN. Kept:.dockerand.vps(the reap and the backup use them).deploy/,deploy-reap.shand the local PoC fileinfra/gitlab/ci/deploy.gitlab-ci.yml(not included) are untouched; #499 deletesinfra/gitlab/.infra/gitlab/vps/README.mdnotes the removal where it described those jobs.The reap keeps a manual trigger so the teardown in
infra/forgejo/SWITCH-DAY.mdstep 1 can run once with every merge request closed.Evidence
mainranreuse-image → build-workspace → build-image → production; each MR ranreviewand its screenshots.After: the inlined config (includes merged into one file) lints clean on the server, and every
needs,extendsand!referenceresolves:pnpm lint,typecheck,test,build,format:checkall green.Merge Danger
Door: one-way-ish
Production stops auto-deploying on merge and keeps serving its current image until Forgejo's first green
maindeploys over it. In code it is a two-way door: reverting restores every job.Blast Radius: deploys
No MR gets a preview after this; previews already running stay until the reap is run by hand. The nightly reap schedule now creates no pipeline (no job matches); deactivate it or leave it until #499.
Refs #498
changed the description
mentioned in issue #498