| commit | ede8a80d816f8c102ed4de13ba25512024582a75 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Fri Dec 11 14:53:50 2020 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Fri Dec 11 14:53:50 2020 +0100 |
| tree | 6ac77e0709b7a1422e240323b43d78b838c93bca | |
| parent | 56a7ae643059875a074ab6e3ca92754520483edd [diff] |
Remove .ijwb and .idea, migrate to import_run_configurations The Bazel IntelliJ team has stated that while checking in the .ijwb folder technically sorta-kinda works, they recommend against it since they cannot guarantee any kind of backwards compatibility. Indeed, bootstrapping a working IDE project from a clean checkout with .ijwb has been a delicate matter in the past and is currently broken again. Do the supported thing instead and nuke .ijwb and .idea and ignore them. The .bazelproject file can then be used to create a new project using File → Import Bazel project, creating the workspace from scratch. Run configurations are now created by the Bazel plugin, and those XML files come with a backwards compatibility promise. This means that we lose all other shared settings except run configurations. If there's particular configs that we want to keep, we need to write custom tooling which mangles the XML configs, which will allows us to deal with backwards compatibility and differences in developer setups (i.e. outside contributors). Test Plan: Cloned the project from scratch, imported the Bazel project, everything worked on the first try :O X-Origin-Diff: phab/D658 GitOrigin-RevId: 979ac5345fd8a5f26a5f8ec3d5882ea477b48a69
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.