commit | afb925b446e4f13a05a36f1d87e6b8a1f5a2e27a | [log] [tgz] |
---|---|---|
author | Leopold <leo@monogon.tech> | Sun Jan 08 16:57:28 2023 +0100 |
committer | Leopold Schabel <leo@monogon.tech> | Mon Jan 16 12:37:40 2023 +0000 |
tree | f0b4cd6185a5d55273b33d0d5952db35204a86f7 | |
parent | 94695969085cb2df182f58ee06443c5d7cf233ec [diff] |
.bazelrc: remove hardcoded resource constraints Let Bazel figure out the appropriate number of jobs and RAM by itself. This should improve default build performance on large machines. One possible caveat: we use genrules that consume excessive CPU on their own (i.e. edk2, kernel...), and removing the jobs limit might cause worse resource contention in some scenarios - but from limited testing, this does not appear to be a problem. Change-Id: Ib96d7953b6530fe202f8b7b0aa160cc7e2f2c35c Reviewed-on: https://review.monogon.dev/c/monogon/+/1070 Tested-by: Jenkins CI Reviewed-by: Serge 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 //...