Release settings
These apply to every release started from this page.
The backend, frontend and test repositories are tagged at the commits this pins.
Name, icon, package ids and tenant pin come from the brand profile.
Leave empty for the ROG host; marsad builds and tests there instead.
Checking for a macOS runner…
Empty means the brand's icon. An uploaded PNG wins over the URL; keep it square, 512 px or more, under 512 KB.
What is going out
Commits on the chosen source that the last official release does not have.
Checklist
Release candidate
Builds and tests everything and stages the backend as a no-traffic candidate. Nothing reaches users or the stores.
Suggested from existing tags.
Creates the tags, starts the release run, and follows it below.
Official release
Re-tags a candidate that passed, at the same commits. The release run goes again in full and the images become latest.
Afterwards: test the candidate, then press promote-backend and deploy-web in the progress panel.
Build another brand
Rebuild a released tag for a different brand: no new tag, no tests, just the packages.
Roll back
Route all traffic to an earlier revision of the live backend.
From the board's deployments, or the deploy job's PREVIOUS_REVISION line.
macOS VM
iPhone builds run on the VM. The pipeline starts it when needed; start it ahead of time here.
Checking…
It holds 6 cores and 12 GB on the build host, so stopping it when no iPhone build is due frees the machine. A release that needs iPhone starts it again by itself; a stop is refused while a build is running.
Recent releases
Deploy runs, newest first, with the manual steps still waiting.
| Started | Tag | Brand | Targets | Status | Waiting | |
|---|---|---|---|---|---|---|
| Loading… | ||||||