commit | 2c6906a62a623d49c6a9c8529b26d692194c1dd5 | [log] [tgz] |
---|---|---|
author | Lorenz Brun <lorenz@monogon.tech> | Wed Jun 15 12:55:45 2022 +0000 |
committer | Lorenz Brun <lorenz@monogon.tech> | Wed Jun 15 13:30:52 2022 +0000 |
tree | a0e91524fde140a3a1ecfcb5d586bed8baaf0f94 | |
parent | 45c196cc0e8a388d6e1d69744c1b8d1b52b4b74e [diff] |
WORKSPACE: clean out unused patch This was added as a transitory measure when I was porting to gomod. Its use was dropped in Kubernetes 1.24 as Kubernetes started pregenerating this themselves. Change-Id: If3cf7577aa03c3779c8347360f0e6f6efe55bb6a Reviewed-on: https://review.monogon.dev/c/monogon/+/771 Tested-by: Jenkins CI Reviewed-by: Mateusz Zalega <mateusz@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 //...