Gitiles
Code Review Sign In
gerrit-dev.monogon.dev / monogon / adb98f9d02a0b2c6b5def344d421a79ab9c6b37e
commitadb98f9d02a0b2c6b5def344d421a79ab9c6b37e[log] [tgz]
authorLorenz Brun <lorenz@monogon.tech>Mon Jul 04 14:09:41 2022 +0000
committerLorenz Brun <lorenz@monogon.tech>Mon Jul 04 15:32:37 2022 +0000
tree3e71b40b2ebb7c0ddae3667b58d9ee85a727526b
parent237cf4076e4314ea98f4d47e9557857ef73f554b [diff]
workspace: support workspace-relative embeds in rules_go

rules_go constrains itself by default to includes from the same
directory or its subdirectories, just like the standard Go compiler.
With Bazel however including things from other packages is very common.
Aliases don't help as Bazel doesn't actually copy the artifacts for
efficiency.

This patches rules_go to also accept Bazel-style embeds.

Change-Id: I8fc9479492da00e463297e11b99ff2a9b88bbfde
Reviewed-on: https://review.monogon.dev/c/monogon/+/820
Tested-by: Jenkins CI
Reviewed-by: Mateusz Zalega <mateusz@monogon.tech>
2 files changed
tree: 3e71b40b2ebb7c0ddae3667b58d9ee85a727526b
  1. build/
  2. intellij/
  3. metropolis/
  4. scripts/
  5. third_party/
  6. .bazelignore
  7. .bazelproject
  8. .bazelrc
  9. .git-ignore-revs
  10. .gitignore
  11. BUILD
  12. CODING_STANDARDS.md
  13. go.mod
  14. go.sum
  15. LICENSE
  16. README.md
  17. WORKSPACE
README.md

Monogon Monorepo

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!

Environment

Our build environment requires a working Podman binary (your distribution should have one).

Usage

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)

IntelliJ

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.

Metropolis

Run a single node cluster

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 //...