diff --git a/docs/versions/8.0.1/reference/flag-cheatsheet.mdx b/docs/versions/8.0.1/reference/flag-cheatsheet.mdx index 6c406ea64def79..b543ea51ae51ae 100644 --- a/docs/versions/8.0.1/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.0.1/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -308,7 +308,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -333,7 +333,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -350,7 +350,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -412,7 +412,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -427,7 +427,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -480,7 +480,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -494,7 +494,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/8.1.1/reference/flag-cheatsheet.mdx b/docs/versions/8.1.1/reference/flag-cheatsheet.mdx index 462f987f84a3a1..23bb4e1df6a842 100644 --- a/docs/versions/8.1.1/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.1.1/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -308,7 +308,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -333,7 +333,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -350,7 +350,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -412,7 +412,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -427,7 +427,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -480,7 +480,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -494,7 +494,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/8.2.1/reference/flag-cheatsheet.mdx b/docs/versions/8.2.1/reference/flag-cheatsheet.mdx index d8c5b8caf93fbf..2d18fc1324cbf0 100644 --- a/docs/versions/8.2.1/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.2.1/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -308,7 +308,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -333,7 +333,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -350,7 +350,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -412,7 +412,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -427,7 +427,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -480,7 +480,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -494,7 +494,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/8.3.1/reference/flag-cheatsheet.mdx b/docs/versions/8.3.1/reference/flag-cheatsheet.mdx index 615ce048ad8ec4..29c33ea348cb3d 100644 --- a/docs/versions/8.3.1/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.3.1/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -308,7 +308,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -333,7 +333,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -350,7 +350,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -412,7 +412,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -427,7 +427,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -480,7 +480,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -494,7 +494,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/8.4.2/reference/flag-cheatsheet.mdx b/docs/versions/8.4.2/reference/flag-cheatsheet.mdx index 15d54c29c4b106..dd868759386c5f 100644 --- a/docs/versions/8.4.2/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.4.2/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -308,7 +308,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -333,7 +333,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -350,7 +350,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -412,7 +412,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -427,7 +427,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -480,7 +480,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -494,7 +494,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/8.5.1/reference/flag-cheatsheet.mdx b/docs/versions/8.5.1/reference/flag-cheatsheet.mdx index 6aba0ae46eea18..6f7944ca3bf8cd 100644 --- a/docs/versions/8.5.1/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.5.1/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -308,7 +308,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -333,7 +333,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -350,7 +350,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -365,7 +365,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -382,7 +382,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -412,7 +412,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -427,7 +427,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -440,7 +440,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -454,7 +454,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -468,7 +468,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -480,7 +480,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -494,7 +494,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/8.6.0/reference/flag-cheatsheet.mdx b/docs/versions/8.6.0/reference/flag-cheatsheet.mdx index 03ddc21c776e9a..d2539867893504 100644 --- a/docs/versions/8.6.0/reference/flag-cheatsheet.mdx +++ b/docs/versions/8.6.0/reference/flag-cheatsheet.mdx @@ -22,7 +22,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -36,7 +36,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -48,7 +48,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -69,7 +69,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -171,7 +171,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -194,7 +194,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -227,7 +227,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -259,7 +259,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -271,7 +271,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -285,7 +285,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_output

+

`--test_output`

@@ -311,7 +311,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -337,7 +337,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -354,7 +354,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -369,7 +369,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -386,7 +386,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -417,7 +417,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -432,7 +432,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -445,7 +445,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -459,7 +459,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -473,7 +473,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -485,7 +485,7 @@ The value to pass as instance_name in the remote execution API. -

--show-timestamps

+

`--show-timestamps`

@@ -499,7 +499,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/9.0.0/reference/flag-cheatsheet.mdx b/docs/versions/9.0.0/reference/flag-cheatsheet.mdx index 97deccdfa4355e..5fbf46bf120ccc 100644 --- a/docs/versions/9.0.0/reference/flag-cheatsheet.mdx +++ b/docs/versions/9.0.0/reference/flag-cheatsheet.mdx @@ -23,7 +23,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -37,7 +37,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -49,7 +49,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -70,7 +70,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -96,7 +96,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -109,7 +109,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -124,7 +124,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -147,7 +147,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -170,7 +170,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -193,7 +193,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -226,7 +226,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -257,7 +257,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -269,7 +269,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -283,7 +283,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_filter

+

`--test_filter`

@@ -300,7 +300,7 @@ debugging. This flag is often used in conjunction with -

--test_output

+

`--test_output`

@@ -325,7 +325,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -350,7 +350,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -367,7 +367,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -382,7 +382,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -399,7 +399,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -429,7 +429,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -444,7 +444,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -457,7 +457,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -471,7 +471,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -485,7 +485,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -497,7 +497,7 @@ The value to pass as instance_name in the remote execution API. -

--show_timestamps

+

`--show_timestamps`

@@ -511,7 +511,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`

diff --git a/docs/versions/9.1.0/reference/flag-cheatsheet.mdx b/docs/versions/9.1.0/reference/flag-cheatsheet.mdx index 8d88b7b40b8bfa..99513c48250516 100644 --- a/docs/versions/9.1.0/reference/flag-cheatsheet.mdx +++ b/docs/versions/9.1.0/reference/flag-cheatsheet.mdx @@ -45,7 +45,7 @@ The following flags are meant to be set explicitly on the command line. -

--config

+

`--config`

@@ -59,7 +59,7 @@ be selected with --config=<group>. -

--keep_going

+

`--keep_going`

@@ -71,7 +71,7 @@ By default, Bazel fails eagerly. -

--remote_download_outputs

+

`--remote_download_outputs`

@@ -92,7 +92,7 @@ and intermediate artifacts that are necessary for local actions. -

--stamp

+

`--stamp`

@@ -119,7 +119,7 @@ The following flags can help you better understand Bazel build or test errors. -

--announce_rc

+

`--announce_rc`

@@ -132,7 +132,7 @@ machine-defined, or project-defined .bazelrc files. -

--auto_output_filter

+

`--auto_output_filter`

@@ -147,7 +147,7 @@ command line. To disable all filtering, set -

--sandbox_debug

+

`--sandbox_debug`

@@ -170,7 +170,7 @@ builds by default and what gets sandboxed, see our -

--subcommands (-s)

+

`--subcommands (-s)`

@@ -194,7 +194,7 @@ a server restart. Toggle these flags with caution. -

--bazelrc

+

`--bazelrc`

@@ -217,7 +217,7 @@ the .bazelrc file>. -

--host_jvm_args

+

`--host_jvm_args`

@@ -250,7 +250,7 @@ For example, the following limits the Bazel heap size to 3GB: -

--output_base

+

`--output_base`

@@ -282,7 +282,7 @@ The following flags are related to Bazel test -

--java_debug

+

`--java_debug`

@@ -294,7 +294,7 @@ Causes Java tests to wait for a debugger connection before being executed. -

--runs_per_test

+

`--runs_per_test`

@@ -308,7 +308,7 @@ flaky tests and see whether a fix causes a test to pass consistently. -

--test_filter

+

`--test_filter`

@@ -325,7 +325,7 @@ debugging. This flag is often used in conjunction with -

--test_output

+

`--test_output`

@@ -351,7 +351,7 @@ The following flags are related to Bazel run. -

--run_under

+

`--run_under`

@@ -377,7 +377,7 @@ options. -

--disk_cache

+

`--disk_cache`

@@ -394,7 +394,7 @@ up Bazel builds by adding -

--jobs

+

`--jobs`

@@ -409,7 +409,7 @@ cluster executes more jobs than you have cores locally. -

--local_resources

+

`--local_resources`

@@ -426,7 +426,7 @@ Limits how much CPU or RAM is consumed by locally running actions. -

--sandbox_base

+

`--sandbox_base`

@@ -457,7 +457,7 @@ options. -

--flaky_test_attempts

+

`--flaky_test_attempts`

@@ -472,7 +472,7 @@ the test summary. -

--remote_cache

+

`--remote_cache`

@@ -485,7 +485,7 @@ speed up Bazel builds. It can be combined with a local disk cache. -

--remote_download_regex

+

`--remote_download_regex`

@@ -499,7 +499,7 @@ patterns may be specified by repeating this flag. -

--remote_executor

+

`--remote_executor`

@@ -513,7 +513,7 @@ a remote execution service. You'll often need to Add -

--remote_instance_name

+

`--remote_instance_name`

@@ -525,7 +525,7 @@ The value to pass as instance_name in the remote execution API. -

--show_timestamps

+

`--show_timestamps`

@@ -539,7 +539,7 @@ quickly understand what step took how long. -

--spawn_strategy

+

`--spawn_strategy`