Skip to content

Skip the cache commit tiers on lean hosts #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
buildpulser merged 1 commit into from
Oct 23, 2026
Merged

Skip the cache commit tiers on lean hosts #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dist/post.js
View file
Open in desktop

Large diffs are not rendered by default.

8 changes: 8 additions & 0 deletions src/post.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -410,6 +410,14 @@ const lane = process.env.BK_CACHE_LANE || '';

// Cap size, then Tier 1 — node-local NVMe. If tier 1 fails there is nothing to push.
pruneCache();

// Lean EC2 hosts keep the buildkit root on the host and the BuildPulse agent commits it
// after the job, so neither tier below applies. Without this the NVMe copy finds no
// /home/runner/buildkit-root and every build ends on a warning plus an error metric.
if (process.env.BP_SUBSTRATE === 'ec2') {
core.info('lean host: the BuildPulse agent commits the layer cache after the job');
process.exit(0);
}
try {
if (PERSISTENT) {
core.info('persistent buildkit root — no NVMe copy tier (root IS the node cache)');
Expand Down
Loading