mirror of
https://github.com/nolen777/eagle0.git
synced 2026-07-28 22:55:41 +00:00
97bf29d4a2
* Fix Bazel Xcode version caching causing CI build failures When Xcode updates on self-hosted runners, Bazel's cached local_config_xcode still references the old version, causing "xcode-locator <old_version> failed" errors. Add sync_bazel_xcode.sh which detects Xcode version changes and runs `bazel sync --configure` to refresh the config without nuking the build cache. Added to all 8 CI workflows that use Bazel. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Use rm of cached repo instead of bazel sync --configure bazel sync --configure requires WORKSPACE mode and fails with bzlmod. Instead, delete the stale local_config_xcode from the output base directly — the next bazel build regenerates it. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Use bazel clean --expunge instead of targeted repo deletion Deleting just local_config_xcode is insufficient — the stale Xcode version is also embedded in cached actions and other toolchain repos. The only reliable fix is a full expunge. Since Xcode updates are infrequent, the one-time rebuild cost is acceptable. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Use action_env to bake Xcode version into cache keys Instead of expunging the cache (which doesn't help with the remote cache anyway), write the Xcode build version to .bazelrc.xcode via --action_env. This makes the version part of every action's cache key, so stale entries in both local and remote caches are naturally ignored after an Xcode update — no deletion needed anywhere. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add expunge back alongside action_env for belt-and-suspenders fix action_env alone isn't enough — local_config_xcode is a cached repository rule that bakes in the old Xcode version before any actions run. Need expunge to clear the local toolchain config, plus action_env to prevent stale remote cache hits afterward. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add Xcode sync to mac_build build-and-sign job The sync step was only in the deploy job, but build-and-sign calls bazel via build_protos.sh before that. This runs on the unity-mac runner which also has the stale Xcode cache. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
46 lines
827 B
Plaintext
46 lines
827 B
Plaintext
opensource_noEdits/
|
|
*.o
|
|
*.a
|
|
*.lib
|
|
*.dSYM/
|
|
*.bundle/
|
|
.DS_Store
|
|
xcuserdata/
|
|
.codelite/
|
|
Makefile
|
|
Release/
|
|
Debug/
|
|
CMakeLists.txt
|
|
clients/unity/eagle0/Assets/Plugins/Grpc.Core/runtimes/ios.meta
|
|
.idea
|
|
target/
|
|
lib_managed/
|
|
src_managed/
|
|
project/boot/
|
|
project/plugins/project/
|
|
project/target/
|
|
bazel-bin
|
|
bazel-eagle0*
|
|
bazel-out
|
|
bazel-testlogs
|
|
.bazelrc.xcode
|
|
.ijwb
|
|
.clwb
|
|
buildWin.sh
|
|
*.psd
|
|
.vscode/
|
|
.lldbinit
|
|
__pycache__/
|
|
scripts/refresh_name_layers/vendor/
|
|
scripts/refresh_name_layers/refresh_name_layers.zip
|
|
.bazelbsp
|
|
.bsp
|
|
.metals
|
|
api_keys.txt
|
|
|
|
src/main/csharp/net/eagle0/clients/unity/eagle0/Assets/GeneratedProtos/
|
|
src/main/csharp/net/eagle0/clients/unity/eagle0/Assets/Plugins/Eagle0Protos/
|
|
src/main/csharp/net/eagle0/clients/unity/eagle0/ProjectSettings/Packages/com.unity.dedicated-server/
|
|
node_modules/
|
|
tools/map_generator/output/
|