| commit | 100e22fac40295424b76fcae5a05eddf0f25d345 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Mon Jun 20 14:23:57 2022 +0000 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Tue Jun 21 11:17:34 2022 +0000 |
| tree | d9bc91fef41712260e7715395aa2b1463800d1b4 | |
| parent | 05e420db50f6d01a9214957dc9e8ac32316525ab [diff] |
m/n/core: fix pstore runnable Make it first signal healthy, then done. Otherwise it seems to panic sometimes. Also move all signalling code to the end of the runnable. Change-Id: I4911f94aafbd324a49f7ff5af9904a778ddb8dce Reviewed-on: https://review.monogon.dev/c/monogon/+/774 Tested-by: Jenkins CI 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 -c dbg
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -c dbg -- kubectl describe
Run tests:
scripts/bin/bazel test -c dbg //...