mirror of
https://github.com/Kilo-Org/kilocode.git
synced 2026-08-28 19:11:03 +08:00
revert(ci): keep Windows off the bun dependency cache
Measured with the Defender exclusions active: Setup Bun ran 83-102s with cache restore vs ~86s with a fresh install — no benefit, plus a save-step cost on non-PR runs. The original reasoning stands.
This commit is contained in:
@@ -40,9 +40,10 @@ runs:
|
||||
shell: bash
|
||||
run: echo "dir=$(bun pm cache)" >> "$GITHUB_OUTPUT"
|
||||
|
||||
# Windows uses this cache again: the old 2m23s restore-vs-1m27s-install measurement # kilocode_change
|
||||
# predates the Defender exclusions, which cover both the bun cache and node_modules. # kilocode_change
|
||||
# Restoring the ~1 GB cache buys nothing on Windows even with Defender exclusions # kilocode_change
|
||||
# (measured 83-102s Setup Bun with cache vs ~86s fresh install); keep Windows off it. # kilocode_change
|
||||
- name: Restore Bun dependencies
|
||||
if: runner.os != 'Windows' # kilocode_change
|
||||
id: bun-cache
|
||||
uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
|
||||
with:
|
||||
@@ -101,8 +102,9 @@ runs:
|
||||
fi
|
||||
shell: bash
|
||||
|
||||
# Do not upload a Windows cache that Windows jobs intentionally never restore. # kilocode_change
|
||||
- name: Save Bun dependencies
|
||||
if: steps.bun-cache.outputs.cache-hit != 'true' && github.event_name != 'pull_request' && github.event_name != 'pull_request_target' # kilocode_change
|
||||
if: runner.os != 'Windows' && steps.bun-cache.outputs.cache-hit != 'true' && github.event_name != 'pull_request' && github.event_name != 'pull_request_target' # kilocode_change
|
||||
uses: actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
|
||||
with:
|
||||
path: ${{ steps.cache.outputs.dir }}
|
||||
|
||||
Reference in New Issue
Block a user