| commit | 7f1cfd4314e3fcef50a109e6749945d93f264812 | [log] [tgz] |
|---|---|---|
| author | ajurkowski <ajurkowski@google.com> | Thu Sep 16 09:21:08 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 16 09:22:46 2021 -0700 |
| tree | 67e9d2d0dcdd6791ca975d3748852b0b152bd183 | |
| parent | 086db164f927cc1d8a0cf432fea1b06e930555c5 [diff] |
Automated rollback of commit 6f5c4bb4d17abd6b9654f255c12775eb35638000. *** Reason for rollback *** Fixed handling of `NoSuchFileException`. *** Original change description *** Automated rollback of commit 8181f0abe6591bc14957e6a941a6556fb040ca9f. *** Reason for rollback *** b/198749645 *** Original change description *** Add a new `FileSystem` method to get a `SeekableByteChannel` for writing files. Add `FileSystem::createSeekableChannel` which allows us to create a `SeekableByteChannel` for file writes. The channel is opened in truncated mode, meaning that it is not suitable for reading existing files. PiperOrigin-RevId: 397097903
{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
