| commit | defff5220d4ed1123a85cf41300eeeeb558b7cc6 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Mon May 16 17:28:16 2022 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Tue May 24 15:31:20 2022 +0000 |
| tree | 9082dd3faaa58a3e219be579b0c7c6138b434b53 | |
| parent | a81096f56a337b5709e7cc692e89cb0e55e45708 [diff] |
metropolis: fix tests using etcd Ever since we bumped etcd, we have started calling integration.BeforeTest. The correct call is BeforeTestExternal, otherwise some internal-etcd-integration-test logic is invoked, which seems to break test error calls (!) in some cases (probably goroutine leak detection, which is enabled by default when using BeforeTest - which we don't care about, as we don't [yet] expect our tests to be fully clean). We also have to modify the harnesses used by curator tests to synchronously terminate the cluster on each test end. Otherwise, etcd will fail due to conflicts on domain sockets on which test members listen. Unfortunately, there doesn't seem to be an easy way to run each cluster/test in a totally separate, non-conflicting socket setup. Change-Id: I2fb1332edb35349b66af131684feb378ae3a13ee Reviewed-on: https://review.monogon.dev/c/monogon/+/688 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
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...