| commit | ac9947fd23ad4dab909a9282ac56fd51dcecb4e4 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Thu Jul 09 18:58:26 2020 +0200 |
| committer | Leopold Schabel <leo@nexantic.com> | Thu Jul 09 18:58:26 2020 +0200 |
| tree | 31ac22eb93c43d6569c79908ea9d446bdc8e6181 | |
| parent | 70f65b237aa29f2e9aced8a4a1e1739b6544cb92 [diff] |
intellij: add launch configuration presets for single node and e2e - Run e2e tests normally with streamed output - Run e2e tests without caching and -c dbg - Run e2e tests without caching, -c dbg and with dlv - Run all tests normally - Run a single node cluster normally - Run a single node cluster with -c dbg Test Plan: Ran 'em all. X-Origin-Diff: phab/D582 GitOrigin-RevId: 6d78ee3ea4e4c4e2c0096fc4e6f449dbcdb333ca
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.