Gitiles
Code Review Sign In
gerrit-dev.monogon.dev / monogon / bf5994514f50390c64c2ae6be2371687d312850c
commitbf5994514f50390c64c2ae6be2371687d312850c[log] [tgz]
authorSerge Bazanski <serge@monogon.tech>Wed Oct 06 00:00:22 2021 +0200
committerSergiusz Bazanski <serge@monogon.tech>Wed Oct 06 14:50:22 2021 +0000
tree679766afdb62bd1721bfb48acb71c394c691f595
parentbf68fa9d8cbf6d283da8d538c1f28d8f53df0fcd [diff]
build/ci: attempt to prevent Jenkins from killing Bazel

Every so often in CI we see the following:

   Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/home/ci/.cache/bazel/_bazel_ci/8746318cfadba75371ec634ee6e84c81/server/jvm.out')

Not sure what causes it, but setting this magical value apparently
causes Jenkins' ProcessTreeKiller to stop killing all subprocesses of an
existing process, which might be causing the above. We'll find out.

Change-Id: Ibe48126dcf547735183c8789260bac6c42a0a10e
Reviewed-on: https://review.monogon.dev/c/monogon/+/347
Reviewed-by: Leopold Schabel <leo@nexantic.com>
1 file changed
tree: 679766afdb62bd1721bfb48acb71c394c691f595
  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. LICENSE
  13. README.md
  14. WORKSPACE
README.md

Monogon Monorepo

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.

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

Run a kubectl command:

scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe

Run tests:

scripts/bin/bazel test //...