Plan: build cloud environments from [install] (SUPER-3017)
Draft
SA
16d ago+604+604+012345678901234567890123456789-0-0-0123456789
Draft for review of the plan only; code follows in separate PRs.
What this is
plans/20261030-0017-environment-builds.md: the ExecPlan for SUPER-3017. It covers building an environment's golden from[install]on demand and daily, keeping the last five goldens with Restore, changing repositories through a build, and the Settings screens.design/environment-builds/index.html: the UI mockup agreed in review. Published copy: https://app.superset.sh/page/environment-builds-super-3017-mockup-w2u7xq
Decisions worth a reviewer's eye (Decision Log in the plan)
- D3: the whole build fits one 300 s job: 45 s for the box, 180 s for
[install], the rest for the snapshot. A cold first build of a large repository may not fit. - D5:
--freshis refused for a golden saved from a workspace unless--discard-workspace-setupis passed. Fresh is CLI only. - D6: daily builds skip free orgs and pause after three failures in a row; a successful manual build resumes them.
- The build never boots the box, so
[setup]never runs in it and no bundle or image release is needed.
PRs that follow
- Build records,
rebuildEnvironment, the build job, tRPC (environment.rebuild,builds,restore), CLI, setup skill docs. - The daily job.
- Changing repositories through a build.
- Desktop screens.
Linear: SUPER-3017
Summary by cubic
Adds the ExecPlan and UI mockup for building cloud environments from [install] (SUPER-3017). The plan covers on-demand and daily builds as QStash jobs, keeping the last five goldens with restore, changing repositories through a build, and the Settings screens. The migration and Milestone 1 code ship in follow-up PRs (#9108, #9110).
Decisions worth reviewing
- A build fits in one job invocation with a 285 s deadline; a cold first build of a large repository may not fit.
- No
--fresh: a build forks the current golden, or starts from the base image when none exists. - Daily builds skip free orgs and pause after three consecutive failures; a successful manual build resumes them.
- Builds never boot the box, so
[setup]never runs and no bundle or image release is needed.