commit | 4b1e37c88d7472fa378393e7a2e545b7a87145c9 | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@monogon.tech> | Tue Sep 28 12:49:15 2021 +0200 |
committer | Sergiusz Bazanski <serge@monogon.tech> | Fri Oct 08 15:34:28 2021 +0000 |
tree | 8f1670f60907fb204bb159f11af637076a43af8f | |
parent | 2f58ac0ba336ad64e5708a4bb72163e368410959 [diff] |
build/fietsje: split into monogon-specific library and cli tool This is a first pass at sightly modularizing fietsje. This allows fietsje-for-Monogon to be used as a Go library, and moves all the toolbase startup logic into its own executable package. This allows us to call fietsje from some multi-purpose CI/check tool that I'm slowly implementing on the side. Fietsje should still be split up further, allowing a generic fietsje library to be used for more than just the Monogon repository - but that will come at a later point. Change-Id: Ic59c0bb954c5416fda95d3604d5aa94553dc1030 Reviewed-on: https://review.monogon.dev/c/monogon/+/331 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 that happens to be publicly available. Nothing to see here, please move along.
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 //...