| commit | 5aa494f9576756992113c72164ec6dc298071276 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Tue May 18 18:57:10 2021 +0200 |
| committer | Sergiusz Bazanski <serge@nexantic.com> | Tue May 18 18:12:39 2021 +0000 |
| tree | 076d9ea79874838d89cffa74f1f0d160a5884422 | |
| parent | 6feb746cfafeedb600ae12e22be910ad376b30a5 [diff] |
build/ci: move Dockerfile, document new CI This moves the Builder Imager Dockerfile into //build/ci, adds some small changes to make it usable as a Jenkins agent base, documents its usage, and adds a script which builds and pushes that image into an external container registry. We also remove the old Phabricator-based CI scripting. Change-Id: I332608f7d7105f675104db3ee2d787b2412fcbe9 Reviewed-on: https://review.monogon.dev/c/monogon/+/28 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-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
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.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)
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 //...