As you may have noticed, we've been transitioning to the bazel build system.

Although most elements are still under development, here are a few notes that could "help us help you."

If your OS or dev container does not already provide it, you will need to install the bazelisk tool, which will automatically switch to the version of bazel specified in the branch you wish to contribute to.

We recommend using brew because the package also installs a symbolic link named bazel: (which is very useful on a daily basis, such as matching examples in the literature)

brew install bazelisk

Otherwise, please choose the bazelisk installation method that suits you best; you can find some of them here:

• Installation
• Requirements

In that case, please consider adding a link to bazelisk named bazel in your PATH.

To help us maintain good bazel file hygiene, please preferably run the version of buildifier specified in the branch you wish to work in:

dda bzl run //bazel/buildifier
# or
bazel run //bazel/buildifier

MODULE.bazel.lock must exhaustively reflect actually used dependencies. After updating any bazel dependency, such as with bazel_dep in a MODULE.bazel file, please run:

bazel mod deps

If you are on the Datadog internal network and want to take advantage of the remote cache, simply add the following line to a user.bazelrc file located at the root of the workspace, or to a .bazelrc file located in your home directory:

common --config=cache