| commit | 18b4d653647c23e3a4cd10832d5d6dbd56a4e37e | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Mon Dec 14 18:27:07 2020 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Mon Dec 14 18:27:07 2020 +0100 |
| tree | d985a3feb246a1e8f365f48659b9e0e5f592ea66 | |
| parent | a4edfa9e12ce6db3216da01be7bf35825893c749 [diff] |
intellij: add localconfig helper Adds a little helper tool which merges a watcherTasks template with the local project config. This restores the functionality lost in D658. Also cured me of any remaining nostalgic feelings towards XML. Test Plan: Deleted all watchers, ran the script, re-opened project, watchers are back and functional. Local watchers with the same name got overwritten. Additional watchers were untouched. X-Origin-Diff: phab/D661 GitOrigin-RevId: 83f7c1506476378145781c816d776fd451aed40c
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.
The following steps are necessary:
Install Google's 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.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)