From f9e8cf8d0daa335b886969b48f5cc443c9e8963a Mon Sep 17 00:00:00 2001 From: Florian Weikert Date: Mon, 12 Oct 2020 14:44:13 +0200 Subject: [PATCH] Fix documentation about release servers (#184) In most cases Bazel binaries are fetched from GCS now, with the exception of forks (still on Github). --- README.md | 5 ++--- bazelisk.go | 1 + 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f731564e..884e8ee9 100644 --- a/README.md +++ b/README.md @@ -51,10 +51,9 @@ Additionally, a few special version names are supported for our official release ## Where does Bazelisk get Bazel from? -By default Bazelisk retrieves the list of Bazel versions from the Bazel GitHub project. If this fails, Bazelisk queries the official Bazel release server instead. -In both cases the actual binaries are downloaded from the release server. +By default Bazelisk retrieves Bazel releases, release candidates and binaries built at green commits from Google Cloud Storage. -As mentioned in the previous section, the `/` version format allows you to use your own Bazel fork instead of working with the official servers: +As mentioned in the previous section, the `/` version format allows you to use your own Bazel fork hosted on GitHub: If you want to create a fork with your own releases, you have to follow the naming conventions that we use in `bazelbuild/bazel` for the binary file names. The URL format looks like `https://github.com//bazel/releases/download//`. diff --git a/bazelisk.go b/bazelisk.go index 9ae856d6..599ed03c 100644 --- a/bazelisk.go +++ b/bazelisk.go @@ -26,6 +26,7 @@ import ( func main() { gcs := &repositories.GCSRepo{} gitHub := repositories.CreateGitHubRepo(core.GetEnvOrConfig("BAZELISK_GITHUB_TOKEN")) + // Fetch releases, release candidates and Bazel-at-commits from GCS, forks from GitHub repos := core.CreateRepositories(gcs, gcs, gitHub, gcs, true) exitCode, err := core.RunBazelisk(os.Args[1:], repos)