| commit | 3bb23219009a98643a562b1e59e3a4080f422c51 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Tue Aug 24 16:27:21 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Tue Aug 24 14:43:38 2021 +0000 |
| tree | 52173a35ecc7029ce0d5cb681bc215a362b0d730 | |
| parent | 41d275a63864e67deacad5b2ec0b435b01984034 [diff] |
build/ci: disable concurrent presubmit builds This prevents more than one presubmit job from executing globally in Jenkins. This will naturally make things more slow, but should let us troubleshoot 'Socket closed' errors. If after this still keeps happening, the theory that Jenkins is somehow scheduling multiple different pipelines per agent/executor (and causing Bazel server conflicts) is wrong and we need to look elsewhere. If it stops the problem, the builds will likely effectively be faster (because we won't waste so much time retriggering builds), and we can then further debug why is it that multiple pipeline stages get scheduled on the same agent/executor. Change-Id: I90a8cdbb6b79fef4b9a33471ff20b821e9988ae9 Reviewed-on: https://review.monogon.dev/c/monogon/+/313 Reviewed-by: Leopold Schabel <leo@nexantic.com>
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 //...