| commit | 57a297179d17671070d98696f342762da05f0060 | [log] [tgz] |
|---|---|---|
| author | tanzhengwei <tanzhengwei@google.com> | Thu Sep 02 08:03:58 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 02 08:05:26 2021 -0700 |
| tree | 31fc1c322343e062d958c07bf4027425ea38423c | |
| parent | 443af630079f2e4b08b7d23268c38a12243d6a77 [diff] |
Automated rollback of commit e8ddcf3abc20c1c4dba150267c94d678975d15e4. *** Reason for rollback *** Breaks internal tests. *** Original change description *** Change Fileset to use providers rather than the FilesetEntry Starlark value type. This allows aspects to traverse Fileset deps correctly and allows constraints to propagate as well. This change removes FilesetEntry completely from the output build graph, and allows all references to this special type to be removed from the core Bazel code, leaving it as just a Google-specific extension. Note that this does not remove the SkyFunction support for Filesets. PiperOrigin-RevId: 394462193
{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
