Put HTTP portions of external downloads behind an interface. This PR is in preparation for a remote implementation of external downloads. It is intended to have no behavior changes, and to split the current `HttpDownloader` logic into: * `HttpDownloader`, which does the actual download with all the fancy concurrency and error handling. * `DownloadManager`, which interacts with `RepositoryCache` and the distdirs. It doesn't know about HTTP any more, instead going through a `Downloader` interface. A future PR will implement a `Downloader` in terms of the bazelbuild/remote-apis protocol and put it behind an `--experimental_remote_downloader` flag. R: @buchgr @dslomov CC: @sstriker Closes #10547. PiperOrigin-RevId: 288884556
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
