commit | d32d1eaec33b9b6e8a2ce6f207892d7a2b236382 | [log] [tgz] |
---|---|---|
author | Leopold Schabel <leo@nexantic.com> | Tue Nov 02 00:06:07 2021 +0100 |
committer | Leopold Schabel <leo@nexantic.com> | Thu Nov 04 12:40:54 2021 +0000 |
tree | dc8e209fe34fbe3575223ac47864b1b7558a9f12 | |
parent | 8d45a0598ae83b8da89442ce8960e64f065182c7 [diff] |
build/ci: install headless JDK As discussed in monogon-dev/monogon#83, we can avoid pulling in a number of unnecessary dependencies by using a headless JDK. Improves upon I4622349, which would break Jenkins. Change-Id: Iff4aef30b9c1ae76293d9a29cf0a86945eabc679 Reviewed-on: https://review.monogon.dev/c/monogon/+/414 Reviewed-by: Sergiusz Bazanski <serge@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
Our build environment requires a working Podman binary (your distribution should have one).
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)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. 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. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon
folder to your idea64.vmoptions
(Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
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.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...