Skip to content

Run Letterboxd match on the OptiPlex rather than the Macs - #6

Merged
alistairjcbrown merged 1 commit into
mainfrom
ccr-16c63d8e-4fuih3
Nov 4, 2026
Merged

alistairjcbrown merged 1 commit into
mainfrom
ccr-16c63d8e-4fuih3

Conversation

@alistairjcbrown

Copy link
Copy Markdown
Member

Moves match_with_letterboxd from [self-hosted, macOS] to [self-hosted, Linux, X64].

  • Only the OptiPlex runners carry both Linux and X64. The Pis are ARM64 and the Macs are macOS, so this targets the Dell without naming a single runner.
  • Any of self-hosted-optiplex-1 to 8 can take the job, so one stuck runner doesn't block the match.
  • The comment above runs-on is updated to say why. The fallback behaviour is unchanged: with no OptiPlex runner online the job waits and the site keeps the previous matched release.

Still to check: the OptiPlex's Letterboxd page cost has not been measured. The first run should finish in about an hour, as it did on the Macs, not the ~4 hours a Pi takes.

If a dedicated label (e.g. optiplex) is added to those runners later, this can become [self-hosted, optiplex], which reads more plainly and won't match any other Linux x86 machine added in future.


Generated by Claude Code

@alistairjcbrown
alistairjcbrown merged commit 4339c9c into main Nov 4, 2026
1 check passed
@alistairjcbrown
alistairjcbrown deleted the ccr-16c63d8e-4fuih3 branch November 4, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants