We got you covered! The root of the repo has a Makefile which you can use for quick actions. is a recursive lookup in Bazel, it will run all tests in all subfolders when set, it is also the easiest way to invoke them.
You can ask Bazel to build the code for you to run in your local machine. Most of these have a verify-* equivalent which will run inside our CI to verify all the scripts ran before merging the PR.
This will update everything you need without having to care about what needs changing. If you just want to do everything at once (and have 5 minutes of your time) you can run:
These are the most common ones which you can use: Just update everything you can!īazel takes care of a lot of automatic code generation for us, from generating CRD updates to updating its own BUILD.bazel files. We also have a few very handy tools inside.
Need to set up a local cluster and install cert-manager in it? Take a look at our kind documentation. No worries we have a lot of helper scripts for you! is a recursive lookup in Bazel, it will run al tests in all subfolders when set, it is also the easiest way to invoke them.įor example bazel test //pkg/.
bazel run //hack/bin:helm will download and run Helm. bazel build //cmd/ctl will build our CLI.īazel test will run any tests for a given packageīazel run is only used to run certain scripts not the compiled code (unlike Go). A quick intro to Bazelīazel build will build and compile code for you e.g. TIP: are you sitting on a corporate network with internal PKI? Bazel does not honor custom CA certificates by default, but depending on your OSĪ clean workaround might be available. TIP: are you using GoLand? Make sure to exclude the bazel- folders! You can do this by right clicking on the folder -> Mark Directory As -> Excluded