Skip to content

Commit 906bfef

Browse files
committed
Update the current status in the README to reflect reality
1 parent 4d5793f commit 906bfef

1 file changed

Lines changed: 13 additions & 10 deletions

File tree

README.md

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -77,16 +77,19 @@ of command line flags and `.bazelrc` files.
7777

7878
## Status
7979

80-
Bonanza is at this point still highly experimental. It is currently
81-
capable of analyzing a slightly altered copy of the bb-storage source
82-
tree and configuring all of the targets contained within. This means
83-
that Bonanza is already complete enough that Starlark rules such as ones
84-
provided by rules\_go, rules\_js, rules\_oci, and rules\_python can be
85-
evaluated and run to completion.
86-
87-
Calls to `ctx.actions.*()` made by rule implementations are currently
88-
still no-ops, meaning that no build graph at the action level is being
89-
constructed. Work on implementing this is expected to start soon.
80+
Bonanza is at this point still highly experimental. However, it is
81+
already capable of building all targets inside a slightly altered copy
82+
of the bb-storage source tree. This means that Bonanza is already
83+
complete enough that C++ compilation works (at least good enough to
84+
build a functioning copy of `protoc`), and that Starlark rules such as
85+
ones provided by bazel-gazelle, rules\_go, rules\_js, rules\_oci, and
86+
rules\_python tend to work as expected.
87+
88+
Bonanza is currently unable to cache build results. This means that
89+
every invocation of `bonanza_bazel` behaves as if a clean build is
90+
performed. Furthermore, Bonanza's storage nodes can only store data in
91+
memory and are unable to evict data if needed. Work on addressing these
92+
limitations will start soon.
9093

9194
## Running Bonanza
9295

0 commit comments

Comments
 (0)