MagicBeanDev/Longshot
MagicBeanDev/Longshot
Watch
74
95
Fork
You've already forked Longshot
 98
Code Issues 232 Pull requests 277 Projects Releases 9 Packages Wiki Activity Actions 806

ci: release builds run only on runners labelled release #728

Merged
HumanBean merged 1 commit from HumanBean/Longshot:ci/release-runner into main 2026-11-15 18:15:36 +00:00
Conversation 0 Commits 1 Files changed 4 +13 -9
HumanBean commented 2026-11-15 06:59:36 +00:00
Owner

Type: ci · Risk: low · Tested on: Linux (actionlint 1.7.12) · Needs: a release runner online

Why

The release builds (an hour and more, 16 GB each) ask for the same runner labels as every pull request's checks, so they can land on any runner, and a runner meant for releases picks up CI too. This gives the release builds a label of their own, release, so they only run on the runners kept for them and CI never takes those runners.

What changed

The builder jobs ask for release instead of ubuntu-latest/ubuntu-24.04; The version and Sign and publish stay on quick. Nothing else in CI moves.

  • workflows: build-linux.yml (appimage) and build-windows.yml (package, vulkan) run on release. They only run when release.yml calls them or by Run workflow.
  • docs/forgejo-runners.md: a release row in the label table (the builders' Docker and disk needs move to it), and a step for registering a release runner with that label only.
  • .forgejo/actionlint.yaml: release is a known self-hosted label.

The launcher's The launcher, both systems build moves to release in MagicBeanDev/LongshotLauncher#83.

Measurements

Verdict: nothing to measure: a workflow label change; actionlint passes on all workflows.

Flags and settings

None

Testing

Tested: actionlint 1.7.12 (the release CI pins, SHA-256 checked) with .forgejo/actionlint.yaml on .forgejo/workflows/*.yml: no findings. A runner labelled release only is registered and online (charles-linux).

Not tested: a release run on it; the next nightly after merge is the test.

Must be tested:

  • a release runner (charles-linux): let the first nightly after merge run, expecting its Linux and Windows builder jobs to run on that runner and the nightly to publish (by hand: each job's page names its runner)

Risks

What could break: a release, nightlies included, waits in the queue while no release runner is online.

Turning it off: revert the commit, or add release to another runner's labels.

Compatibility: Nothing changes

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named). Left to CI.
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Docs updated.
**Type:** ci · **Risk:** low · **Tested on:** Linux (actionlint 1.7.12) · **Needs:** a `release` runner online ## Why The release builds (an hour and more, 16 GB each) ask for the same runner labels as every pull request's checks, so they can land on any runner, and a runner meant for releases picks up CI too. This gives the release builds a label of their own, `release`, so they only run on the runners kept for them and CI never takes those runners. ## What changed The builder jobs ask for `release` instead of `ubuntu-latest`/`ubuntu-24.04`; *The version* and *Sign and publish* stay on `quick`. Nothing else in CI moves. - workflows: `build-linux.yml` (`appimage`) and `build-windows.yml` (`package`, `vulkan`) run on `release`. They only run when `release.yml` calls them or by *Run workflow*. - `docs/forgejo-runners.md`: a `release` row in the label table (the builders' Docker and disk needs move to it), and a step for registering a release runner with that label only. - `.forgejo/actionlint.yaml`: `release` is a known self-hosted label. The launcher's *The launcher, both systems* build moves to `release` in [MagicBeanDev/LongshotLauncher#83](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/pulls/83). ## Measurements **Verdict:** nothing to measure: a workflow label change; actionlint passes on all workflows. ### Flags and settings None ## Testing **Tested:** actionlint 1.7.12 (the release CI pins, SHA-256 checked) with `.forgejo/actionlint.yaml` on `.forgejo/workflows/*.yml`: no findings. A runner labelled `release` only is registered and online (charles-linux). **Not tested:** a release run on it; the next nightly after merge is the test. **Must be tested:** - a `release` runner (charles-linux): let the first nightly after merge run, expecting its Linux and Windows builder jobs to run on that runner and the nightly to publish (by hand: each job's page names its runner) ## Risks **What could break:** a release, nightlies included, waits in the queue while no `release` runner is online. **Turning it off:** revert the commit, or add `release` to another runner's labels. **Compatibility:** Nothing changes ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [ ] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). Left to CI. - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Docs updated.
ci: release builds run only on runners labelled release
Some checks failed
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Details
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
Details
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
Details
Third-party parts / The same as upstream (pull_request) Has been skipped
Details
CI / Conventional Commit title (pull_request) Successful in 3s
Details
CI / Workflow lint (actionlint) (pull_request) Successful in 7s
Details
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 5s
Details
Third-party parts / As their notes say (pull_request) Successful in 8s
Details
Website / Website on Cloudflare (pull_request_target) Has been skipped
Details
PR description / Description follows the template (pull_request_target) Failing after 4s
Details
e9fadf3ba0 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean changed title from WIP: ci: release builds run only on runners labelled release to ci: release builds run only on runners labelled release 2026-11-15 18:15:01 +00:00
HumanBean deleted branch ci/release-runner 2026-11-15 18:15:36 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area/accessibility
Barriers for people with disabilities

  
area/audio
Sound and music

  
area/input
Controllers, keyboard, mouse

  
area/install
Installing, updating, building from your game

  
area/menu
In-game menu and settings

  
area/renderer
Vulkan renderer, shaders, effects

  
area/saves
Save files

  
area/upscaling
DLSS, FSR, frame generation

  
beanstalk: approved @ 1697603
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 2c5a62e
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 4fd82b7
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 64d6d09
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 6f91fae
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 70a78f9
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 8d361dc
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 9d8356e
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ abf2227
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ d82f202
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ e5f1e40
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ ee8ab5f
Set by Beanstalk for show; the farm's database is what counts

  
ci: approved
A maintainer approved CircleCI for this fork PR (sticky; removed after 14 quiet days)

  
good first issue
A good start for a new contributor

  
gpu/amd
AMD GPUs

  
gpu/igpu
Integrated GPUs

  
gpu/intel
Intel GPUs

  
gpu/nvidia
NVIDIA GPUs

  
help wanted
Extra hands or knowledge wanted

  
kind
bug
 Something doesn't work as it should

  
kind
chore
 Build, CI, dependencies, tidying

  
kind
docs
 Documentation

  
kind
feature
 A new feature or an improvement

  
kind
performance
 Frame rate, frame time, loading, memory

  
kind
question
 A question rather than a change

  
needs measurements
Waiting for before/after measurements

  
platform/linux
Affects Linux (a change for every system carries both Windows and Linux)

  
platform/macos
macOS (Apple silicon or Intel Macs)

  
platform/steam-deck
Steam Deck

  
platform/windows
Affects Windows (a change for every system carries both Windows and Linux)

  
preview
Maintainers: deploy a preview of this PR's website (read its changes first). Removed after the run.

  
priority
critical
 Crashes, data loss, or blocks most players

  
priority
high
 Important: next in line

  
priority
low
 Nice to have

  
regression
Worked in an earlier build, broken in a newer one: highest priority, above other bugs

  
status
blocked
 Waits on something else first

  
status
confirmed
 Reproduced or agreed on

  
status
duplicate
 Already reported or proposed

  
status
invalid
 Not a problem in this project

  
status
needs-info
 Waiting for more information from the reporter

  
status
wontfix
 Will not be worked on

  
testing wanted
Wanted: a test on other hardware (posts a test request in #test-requests)

  
ci: approved
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
beanstalk: approved @ 1697603
beanstalk: approved @ 2c5a62e
beanstalk: approved @ 4fd82b7
beanstalk: approved @ 64d6d09
beanstalk: approved @ 6f91fae
beanstalk: approved @ 70a78f9
beanstalk: approved @ 8d361dc
beanstalk: approved @ 9d8356e
beanstalk: approved @ abf2227
beanstalk: approved @ d82f202
beanstalk: approved @ e5f1e40
beanstalk: approved @ ee8ab5f
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!728
No description provided.