Skip to content

📖 Document RBE_platform cache-silo-key for distributed builds #36

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

Open
Lambourl wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

📖 Document RBE_platform cache-silo-key for distributed builds #36

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
9 changes: 8 additions & 1 deletion 0352-distributed-builds.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,4 +79,11 @@ cmake-re --host --distributed --build ./build -j1000
> ```bash
> export RBE_remote_disabled="true"
> ```
> 💡 Don't forget to ajdust the number of jobs `-j` used for the build, to avoid overloading your local machine, when building with `RBE_remote_disabled`.
> 💡 Don't forget to ajdust the number of jobs `-j` used for the build, to avoid overloading your local machine, when building with `RBE_remote_disabled`.

> ## 🧹 How to force a clean cache for a `--distributed --build`?
> Sometimes it may be necessary to ensure a build doesn't reuse any previously cached remote actions (_e.g._ investigating a flaky build or simply starting fresh). This can be done by passing a `cache-silo-key` via the `RBE_platform` environment variable:
>
> ```bash
> export RBE_platform="cache-silo-key=<my_unique_silo_key>"
> ```