Bazel DevSite: Replace docs.bazel.build references under //third_part…

…y/bazel.

The new site lives at https://bazel.build.

PiperOrigin-RevId: 441533545

README.md

@@ -23,23 +23,23 @@ Build and test software of any size, quickly and reliably.
 
 ## Getting Started
 
-  * [Install Bazel](https://docs.bazel.build/install.html)
-  * [Get started with Bazel](https://docs.bazel.build/getting-started.html)
+  * [Install Bazel](https://bazel.build/install)
+  * [Get started with Bazel](https://bazel.build/contribute/getting-started)
   * Follow our tutorials:
 
-    - [Build C++](https://docs.bazel.build/tutorial/cpp.html)
-    - [Build Java](https://docs.bazel.build/tutorial/java.html)
-    - [Android](https://docs.bazel.build/tutorial/android-app.html)
-    - [iOS](https://docs.bazel.build/tutorial/ios-app.html)
+    - [Build C++](https://bazel.build/tutorials/cpp)
+    - [Build Java](https://bazel.build/tutorials/java)
+    - [Android](https://bazel.build/tutorials/android-app)
+    - [iOS](https://bazel.build/tutorials/ios-app)
 
 ## Documentation
 
-  * [Bazel command line](https://docs.bazel.build/user-manual.html)
-  * [Rule reference](https://docs.bazel.build/be/overview.html)
-  * [Use the query command](https://docs.bazel.build/query.html)
-  * [Extend Bazel](https://docs.bazel.build/skylark/concepts.html)
-  * [Write tests](https://docs.bazel.build/test-encyclopedia.html)
-  * [Roadmap](https://bazel.build/roadmap.html)
+  * [Bazel command line](https://bazel.build/docs/user-manual)
+  * [Rule reference](https://bazel.build/reference/be/overview)
+  * [Use the query command](https://bazel.build/reference/query)
+  * [Extend Bazel](https://bazel.build/rules/concepts)
+  * [Write tests](https://bazel.build/reference/test-encyclopedia)
+  * [Roadmap](https://bazel.build/community/roadmaps)
   * [Who is using Bazel?](https://github.com/bazelbuild/bazel/wiki/Bazel-Users)
 
 ## Reporting a Vulnerability

scripts/bazel-complete-template.bash

@@ -537,7 +537,7 @@ _bazel__all_configs() {
 
   # Start out getting a list of all RC files that we can look for configs in
   # This respects the various command line options documented at
-  # https://docs.bazel.build/versions/2.0.0/guide.html#bazelrc
+  # https://bazel.build/docs/bazelrc
   rc_files=$(_bazel__rc_files "$workspace")
 
   # Commands can inherit configs from other commands, so build up command_match, which is

scripts/bootstrap/compile.sh

@@ -185,7 +185,7 @@ the protoc compiler (as we prefer not to version generated files).
   compile.sh on the unpacked archive.
 
 The full install instructions to install a release version of bazel can be found
-at https://docs.bazel.build/install-compile-source.html
+at https://bazel.build/install/compile-source
 For a rationale, why the bootstrap process is organized in this way, see
 https://bazel.build/designs/2016/10/11/distribution-artifact.html
 --------------------------------------------------------------------------------

scripts/packages/bazel.sh

@@ -197,7 +197,7 @@ if [[ ! -x $BAZEL_REAL ]]; then
     echo "  sudo apt update && sudo apt install bazel-${bazel_version}"
     echo ""
     echo "If this doesn't work, check Bazel's installation instructions for help:"
-    echo "  https://docs.bazel.build/versions/main/install-ubuntu.html") 2>&1
+    echo "  https://bazel.build/install/ubuntu") 2>&1
   else
     (echo ""
     echo "Bazel binaries for all official releases can be downloaded from here:"

scripts/packages/chocolatey/bazel.nuspec.template

@@ -45,7 +45,7 @@ This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Refe
     <licenseUrl>https://github.com/bazelbuild/bazel/tree/master/LICENSE</licenseUrl>
     <requireLicenseAcceptance>true</requireLicenseAcceptance>
     <projectSourceUrl>https://github.com/bazelbuild/bazel.git</projectSourceUrl>
-    <docsUrl>https://docs.bazel.build/versions/main/getting-started.html</docsUrl>
+    <docsUrl>https://bazel.build/contribute/getting-started</docsUrl>
     <mailingListUrl>https://groups.google.com/forum/#!forum/bazel-discuss</mailingListUrl>
     <bugTrackerUrl>https://github.com/bazelbuild/bazel/issues</bugTrackerUrl>
     <tags>bazel build automation</tags>

src/main/java/com/google/devtools/build/lib/analysis/starlark/FunctionTransitionUtil.java

@@ -127,8 +127,7 @@ static ImmutableMap<String, BuildOptions> applyAndValidate(
    *
    * <p>Transitions can also explicitly set --platforms to be clear what platform they set.
    *
-   * <p>Platform mappings:
-   * https://docs.bazel.build/versions/main/platforms-intro.html#platform-mappings.
+   * <p>Platform mappings: https://bazel.build/concepts/platforms-intro#platform-mappings.
    *
    * <p>This doesn't check that the changed value is actually different than the source (i.e.
    * setting {@code --cpu=foo} when {@code --cpu} is already {@code foo}). That could unnecessarily
@@ -151,7 +150,7 @@ private static void checkForDenylistedOptions(StarlarkDefinedConfigTransition tr
     if (transition.getOutputs().contains("//command_line_option:define")) {
       throw new ValidationException(
           "Starlark transition on --define not supported - try using build settings"
-              + " (https://docs.bazel.build/skylark/config.html#user-defined-build-settings).");
+              + " (https://bazel.build/rules/config#user-defined-build-settings).");
     }
   }
 

src/main/starlark/builtins_bzl/common/java/compile_action.bzl

@@ -111,7 +111,7 @@ def compile_action(
         compilation and not at runtime.
       strict_deps: (str) A string that specifies how to handle strict deps.
         Possible values: 'OFF', 'ERROR', 'WARN' and 'DEFAULT'. For more details
-        see https://docs.bazel.build/versions/main/bazel-user-manual.html#flag--strict_java_deps.
+        see https://bazel.build/docs/user-manual#strict-java-deps.
         By default 'ERROR'.
       enable_compile_jar_action: (bool) Enables header compilation or ijar
         creation. If set to False, it forces use of the full class jar in the

src/test/java/com/google/devtools/build/lib/rules/android/AndroidPlatformsTest.java

@@ -26,8 +26,7 @@
 import org.junit.runners.JUnit4;
 
 /**
- * Tests Android support for Blaze's platforms API
- * (https://docs.bazel.build/versions/main/platforms-intro.html).
+ * Tests Android support for Blaze's platforms API (https://bazel.build/concepts/platforms-intro).
  *
  * <p>This only provides the first-level of testing: that <code>--platforms</code> settings directly
  * impact toolchain selection in expected ways. Devs can lean on this test for quick interactive

tools/build_defs/repo/utils.bzl

@@ -219,7 +219,7 @@ def maybe(repo_rule, name, **kwargs):
     """Utility function for only adding a repository if it's not already present.
 
     This is to implement safe repositories.bzl macro documented in
-    https://docs.bazel.build/versions/main/skylark/deploying.html#dependencies.
+    https://bazel.build/rules/deploying#dependencies.
 
     Args:
         repo_rule: repository rule function.

tools/config/common_settings.bzl

@@ -22,7 +22,7 @@ These rules return a BuildSettingInfo with the value of the build setting.
 For label-typed settings, use the native label_flag and label_setting rules.
 
 More documentation on how to use build settings at
-https://docs.bazel.build/versions/main/skylark/config.html#user-defined-build-settings
+https://bazel.build/rules/config#user-defined-build-settings
 """
 
 BuildSettingInfo = provider(

tools/cpp/clang_installation_error.bat.tpl

@@ -18,7 +18,7 @@ echo. 1>&2
 echo The target you are compiling requires the Clang compiler. 1>&2
 echo Bazel couldn't find a valid Clang installation on your machine. 1>&2
 %{clang_error_message}
-echo Please check your installation following https://docs.bazel.build/versions/main/windows.html#using 1>&2
+echo Please check your installation following https://bazel.build/docs/windows#using 1>&2
 echo. 1>&2
 
 exit /b 1

tools/cpp/vc_installation_error.bat.tpl

@@ -18,7 +18,7 @@ echo. 1>&2
 echo The target you are compiling requires Visual C++ build tools. 1>&2
 echo Bazel couldn't find a valid Visual C++ build tools installation on your machine. 1>&2
 %{vc_error_message}
-echo Please check your installation following https://docs.bazel.build/versions/main/windows.html#using 1>&2
+echo Please check your installation following https://bazel.build/docs/windows#using 1>&2
 echo. 1>&2
 
 exit /b 1