Repository navigation
ci: move Actions jobs to the office VM fleet - #61
Merged
Merged
Conversation
Member
|
why are we moving actions back to the machine again? it ended up being such a time sink last time |
tim-thacker-nullify
approved these changes
Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Actions repository CI and releases consume Blacksmith despite available office capacity.
A dedicated repository runner slot is being provisioned on the first office host. The shared fleet uses a fresh VM root and Docker daemon per job, with a private persistent cache disk. No organization runner token is required.
Companion fleet implementation: https://github.com/Nullify-Platform/nullify/pull/14966.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.