| commit | ab4ef137f84411197c20e477aa8d7dd23f82d8ea | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Fri Sep 24 13:58:13 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Mon Sep 27 18:58:01 2021 +0000 |
| tree | 30d663886742a10d2fb499b21f4f836560fb300c | |
| parent | cbd02be30a3960034ba1be55eabf0aa185604499 [diff] |
build/toolbase/gotoolchain: init Another piece of the toolbase puzzle, this one is a library which provides information about the Go SDK picked by Bazel/rules_go, and allows to build tools that call the `go` tool. This is effectively the logic from //build/fietsje:def.bzl, but rewritten to be reusable. In a later CL, we will make Fietsje use this logic instead of its existing starlark/shell magic. Change-Id: I2be723089410c81843b54df77bcd665a4e050cbb Reviewed-on: https://review.monogon.dev/c/monogon/+/329 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 //...