Gitiles
Code Review Sign In
gerrit-dev.monogon.dev / monogon / 023093c104fbddc568e624949ec68a5722dcd180
commit023093c104fbddc568e624949ec68a5722dcd180[log] [tgz]
authorLeopold Schabel <leo@nexantic.com>Tue Dec 15 18:48:19 2020 +0100
committerLeopold Schabel <leo@nexantic.com>Tue Dec 15 18:48:19 2020 +0100
tree497fe0f51477767642ad885d089daf9e5659d639
parent18b4d653647c23e3a4cd10832d5d6dbd56a4e37e [diff]
intellij: add run configurations for fietsje and gazelle

Test Plan: Did the thing

X-Origin-Diff: phab/D662
GitOrigin-RevId: a2b6da33c09256e78774e83e84972034131fcb77
3 files changed
tree: 497fe0f51477767642ad885d089daf9e5659d639
  1. build/
  2. core/
  3. intellij/
  4. scripts/
  5. third_party/
  6. .bazelignore
  7. .bazelproject
  8. .bazelrc
  9. BUILD
  10. nogo_config.json
  11. README.md
  12. WORKSPACE
README.md

Nexantic monorepo

This is the monorepo storing all of nexantic's internal projects and libraries.

Environment

We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.

For better reproducibility, all builds are executed in containers.

Usage

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)

Run a single node cluster

Launch the node:

bazel run //:launch

Run a kubectl command:

bazel run //core/cmd/dbg -- kubectl describe

IntelliJ

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)