tag	99aa6484103c9c137fcd6076f502b6040d50c756
tagger	Alex Eagle <eagle@post.harvard.edu>	Sun Jun 13 07:27:14 2021 -0700
object	69b0eba849c168e70511aee60b87d13147dfe958

commit	69b0eba849c168e70511aee60b87d13147dfe958	[log] [tgz]
author	Alex Eagle <eagle@post.harvard.edu>	Sun Jun 13 07:25:59 2021 -0700
committer	Alex Eagle <eagle@post.harvard.edu>	Sun Jun 13 07:27:06 2021 -0700
tree	deb8dbe7f98b6d0f87c670c2ab7754a9743dd5c5
parent	6384bc3c7a33b3e4efebdb7ba6864d6b90728c8e [diff]

tree: deb8dbe7f98b6d0f87c670c2ab7754a9743dd5c5

README.md

aspect-cli

This is the frontend for the Aspect build tool. It is currently just a wrapper around bazelisk or bazel, meant to install in tools/bazel.

In the future, we might totally replace the bazel C++ client, and this tool would be a gRPC client of the bazel server.

TODOs

[ ] figure out how to cut and host a release GH Action to cut/publish release whenever a tag is pushed upstream
[ ] document lots of ways to install, including a bash one-liner
[ ] help user ensure bash/zsh completion working
[ ] warn user if Bazel version is floating (no bazelisk, or using latest in .bazelversion, or no .bazelversion)

I can find that Aspect is an easier-to-use wrapper and feel motivated and comfortable to try it immediately.

From aspect.build/install I quickly pick an Installation option, and am guided through to successful install.

The first time I run aspect in interactive mode,

I choose whether I want to install for all users of my workspace, in which case a bootstrap bit is added to tools/bazel ensuring that the tool is downloaded and spawned for anyone cloning my repo.