| commit | a8e23543e792505ea8a40bf544d857163696a25b | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Wed Mar 30 19:57:32 2022 +0200 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Mon Apr 04 09:10:38 2022 +0000 |
| tree | f496a4661b78c07d35d95fef7bc6fb4232d2db5d | |
| parent | d23365d8645d1c7839a49af509af283ee1d0cc4f [diff] |
scripts/bin/bazel: be smart about allocating TTYs Allocating a TTY when output is being redirected results in improper mapping of stdout/stderr and everything gets mangled into stdout. This breaks scripting our wrapped Bazel. This changes the wrapper to only allocate a TTY if the output is one as well. Change-Id: I5683020b5d89f3a7c7760db0fce3e9e8c628d326 Reviewed-on: https://review.monogon.dev/c/monogon/+/643 Reviewed-by: Leopold Schabel <leo@nexantic.com>
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 //...