| commit | c39be6c8b71edfc97a4f4b6054c8e712e551e83e | [log] [tgz] |
|---|---|---|
| author | wyv <wyv@google.com> | Mon Aug 30 09:38:48 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 30 09:40:46 2021 -0700 |
| tree | 548f21ed996c7c9f1839f11b8d7ab4f7a8cb86e2 | |
| parent | e70d9e9e12d82890d41e4d0edcab4d722aad9ff0 [diff] |
bzlmod: create a base class for repository_ctx (https://github.com/bazelbuild/bazel/issues/13316) This base class contains methods to be shared between repository_ctx and module_ctx. In other words, the following methods are moved from repository_ctx to the new StarlarkBaseExternalContext: * `path`: needed to traverse the file system * `os`: needed for OS-specific information and env variables * `read`: needed to read files * `execute`: needed to perform arbitrary operations * `which`: needed to locate tools on PATH The other methods are left out because they're mostly useful for creating files, which module extensions are discouraged from (since the files created in such a way aren't accessible later, unlike those created by repo rules). We'd ideally also need an "http_get" method later. This CL also changes the handling of marker data in repository_ctx (now in the base class), so that instead of directly writing entries into a marker data map, we collect those entries into a separate map. After the context object is used, that separate map can then be read and processed (so repository_ctx can put it into marker data and module_ctx will likely want to write it into the lockfile). PiperOrigin-RevId: 393790084
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
