| commit | e8c5fb387831fe9ff8bd41462176805a9c382999 | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Fri Sep 27 08:30:28 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 27 08:31:56 2024 -0700 |
| tree | abe4a13f84827ff94112a16e6d321e2aaf7d0d58 | |
| parent | db4a400806cee783cdcf8e4e67403f7a6ece028c [diff] |
Automated rollback of commit 8ef7b705bb33de6ee9025c01bdf65a23f73926e3. *** Reason for rollback *** The experiment with using sqlite didn't pan out. We might find other uses for it in the future, but we can always resurrect it from version control; no need to saddle Bazel with the additional dependency until then. *** Original change description *** Implement a JNI wrapper around SQLite. This will be used by the implementation of garbage collection for the disk cache, as discussed in https://github.com/bazelbuild/bazel/issues/5139 and the linked design doc. I judge this to be preferred over https://github.com/xerial/sqlite-jdbc for the following reasons: 1. It's a much smaller dependency. 2. The JDBC API is too generic and becomes awkward to use when dealing with the peculiarities of SQLite. 3. We can (more easily) compile it from source for all host platforms, including the BSDs. *** PiperOrigin-RevId: 679600756 Change-Id: Ic3748fa30404a31504426c523c9b9a60ec451863
{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
