Install the Bazel Homebrew package directly

[NashMiao]

I try to install bazel in the way provided by documents over and over again, but it always failed :

$ brew install bazelbuild/tap/bazel
Updating Homebrew...
==> Installing bazel from bazelbuild/tap
==> Downloading https://releases.bazel.build/3.1.0/release/bazel-3.1.0-installer-darwin-x86_64.sh
-=O=-            #     #     #     #                                          
curl: (7) Failed to connect to releases.bazel.build port 443: Operation timed out
Error: An exception occurred within a child process:
  DownloadError: Failed to download resource "bazel"
Download failed: https://releases.bazel.build/3.1.0/release/bazel-3.1.0-installer-darwin-x86_64.sh

However, I found we can install bazel directly with Homebrew successfully:

brew install bazel

Here is the information:

$ brew info bazel
bazel: stable 3.1.0 (bottled)
Google's own build tool
https://bazel.build/
Not installed
From: https://mirrors.tuna.tsinghua.edu.cn/git/homebrew/homebrew-core.git/Formula/bazel.rb
==> Dependencies
Build: [email protected] ✔
Required: openjdk@11 ✘
==> Requirements
Required: macOS >= 10.10 ✔
==> Analytics
install: 4,734 (30 days), 17,069 (90 days), 70,323 (365 days)
install-on-request: 4,434 (30 days), 15,988 (90 days), 65,300 (365 days)
build-error: 0 (30 days)

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[NashMiao]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[tetromino]

The actual problem appears to be that https://releases.bazel.build is not accessible from China.

The two formulas (bazelbuild/tap/bazel vs. the default bazel) are actually different - bazelbuild/tap/bazel installs our official binary, the default bazel formula installs a binary built by the Homebrew project from source. I think for now we want to encourage the bazelbuild/tap one (since we can better control that our users get a good experience) - see #11243.

But obviously we need to fix connectivity from China.

[NashMiao]

Thank you for your answer. After reading #11243, I fully agree with you. Now, maybe the server's network needs to be improved.