| Build the APK with buck2, from pins rather than from a second checkout a71ef8f nandi 19d ago | 1 | load("@prelude//platforms:defs.bzl", "host_configuration") |
| 2 | load(":defs.bzl", "execution_platform") |
| 3 | |
| 4 | # Where every action runs: locally, against the BuildBuddy cache. The same |
| 5 | # arrangement jolt-native uses, and registered the same two ways — `[build] |
| 6 | # execution_platforms` in .buckconfig and `[parser] target_platform_detector_spec` |
| 7 | # there too, since setting only the first leaves toolchain-owned actions on the |
| 8 | # prelude's uncached default. |
| 9 | execution_platform( |
| 10 | name = "cache", |
| 11 | cpu_configuration = host_configuration.cpu, |
| 12 | os_configuration = host_configuration.os, |
| 13 | use_windows_path_separators = host_info().os.is_windows, |
| 14 | visibility = ["PUBLIC"], |
| 15 | ) |
| 16 | |
| 17 | # The same platform, allowed to dispatch. Most of this graph cannot use it: the |
| 18 | # packaging steps name an Android SDK, a Chez cross build and an OpenSSL by |
| 19 | # absolute path, and a worker has none of them. The boot image compile is the |
| 20 | # one that could, which is why jolt reaches it through a manifest rather than a |
| 21 | # path — see android/BUCK. |
| 22 | execution_platform( |
| 23 | name = "remote", |
| 24 | cpu_configuration = host_configuration.cpu, |
| 25 | os_configuration = host_configuration.os, |
| 26 | remote_enabled = True, |
| 27 | remote_execution_properties = { |
| 28 | "OSFamily": "Linux", |
| 29 | "container-image": "docker://gcr.io/flame-public/rbe-ubuntu24-04:latest", |
| 30 | }, |
| 31 | use_windows_path_separators = host_info().os.is_windows, |
| 32 | visibility = ["PUBLIC"], |
| 33 | ) |