commit | cbd02be30a3960034ba1be55eabf0aa185604499 | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@monogon.tech> | Fri Sep 24 13:39:12 2021 +0200 |
committer | Sergiusz Bazanski <serge@monogon.tech> | Mon Sep 27 18:58:01 2021 +0000 |
tree | eb64c22a5851773ade075837cf3c4a040c54181b | |
parent | c72aa433ff68b76317233ba8805d55845e9efd1a [diff] |
build/toolbase: init In an effort to better the developer/CI experience, I'm moving some of our presubmit checks into a Go tool. This is a helper library that will be used to interact with a Monogon workspace checkout from Go, both in the new presubmit tool but also any other future tools that would like to operate on source code. Change-Id: Ie5f1b1d0153a1c853c241e167d2d3a469c636c94 Reviewed-on: https://review.monogon.dev/c/monogon/+/328 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 //...