bluejay/bluejay-infra
1
0
Fork 0
Code Issues Pull Requests 14 Actions Packages Projects Releases Wiki Activity

runners: add github-runner-updater Deployment #29

Merged
bluejay merged 1 commits from runners/add-updater-deployment-2026-05-26 into main 2026-05-26 03:24:23 +00:00
Conversation 0 Commits 1 Files Changed 2 +136
bluejay commented 2026-05-26 03:23:43 +00:00
Owner
Copy Link

FlowerCore.Updater had only the offline bluejay-ws-sandbox-1 Windows runner registered (the specialized fcsetup E2E target) and no Linux self-hosted runner, leaving the repo with no Linux PR-CI capacity for any future workflow.

Modeled on github-runner-pimanager (Sprint 32 long-tail final entry, 2026-05-25); two replicas with per-pod emptyDir caches.

Also registers github-runner-updater in the LinuxRunnerRepos + ScaledLinuxRunnerDeployments fleet-lint sets so future suite repairs treat the entry as canonically required.

Pre-existing lint failures on this file family (6 total) are orthogonal: initContainer single-container count assertion + fc-updater IngressRoute POST allowlist + DM ApplicationSet convention drift � not introduced by this change.

Verified locally: dotnet test BluejayInfraLint baseline = 6 failed / 54 passed BEFORE this commit; after this commit = 6 failed / 54 passed (same failures).

FlowerCore.Updater had only the offline bluejay-ws-sandbox-1 Windows runner registered (the specialized fcsetup E2E target) and no Linux self-hosted runner, leaving the repo with no Linux PR-CI capacity for any future workflow. Modeled on github-runner-pimanager (Sprint 32 long-tail final entry, 2026-05-25); two replicas with per-pod emptyDir caches. Also registers github-runner-updater in the LinuxRunnerRepos + ScaledLinuxRunnerDeployments fleet-lint sets so future suite repairs treat the entry as canonically required. Pre-existing lint failures on this file family (6 total) are orthogonal: initContainer single-container count assertion + fc-updater IngressRoute POST allowlist + DM ApplicationSet convention drift � not introduced by this change. Verified locally: dotnet test BluejayInfraLint baseline = 6 failed / 54 passed BEFORE this commit; after this commit = 6 failed / 54 passed (same failures).
bluejay added 1 commit 2026-05-26 03:23:50 +00:00
runners: add github-runner-updater Deployment 59543016c0 
FlowerCore.Updater had only the offline bluejay-ws-sandbox-1 Windows
runner registered (the specialized fcsetup E2E target) and no Linux
self-hosted runner, leaving the repo with no Linux PR-CI capacity for
any future workflow. Modeled on github-runner-pimanager (Sprint 32
long-tail final entry, 2026-05-25); two replicas with per-pod emptyDir
caches to keep ReadWriteOnce PVC contention out of the picture.

Also registers github-runner-updater in the LinuxRunnerRepos +
ScaledLinuxRunnerDeployments fleet-lint sets so future suite repairs
treat the entry as canonically required (the 6 pre-existing lint
failures on this file family are orthogonal: initContainer single-
container count assertion + fc-updater IngressRoute POST allowlist
+ DM ApplicationSet convention drift).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bluejay merged commit 0d2090fe81 into main 2026-05-26 03:24:23 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bluejay
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bluejay/bluejay-infra#29
Delete Branch "runners/add-updater-deployment-2026-05-26"

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?