| commit | 6feb746cfafeedb600ae12e22be910ad376b30a5 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Tue May 18 15:49:15 2021 +0200 |
| committer | Sergiusz Bazanski <serge@nexantic.com> | Tue May 18 15:37:38 2021 +0000 |
| tree | 6b8f67cc7f183cfaa3b533a20d069abd1e7f3b07 | |
| parent | 99d210d48afc2207ffb4064c58068faa9449a981 [diff] |
build/ci: add presubmit Jenkinsfile This implements a basic presubmit Jenkinsfile which should be consumed (in this CR already) by CI machinery running against review.monogon.dev. This presubmit exercises the same build targets as the old, internal Phabricator CI. The build executing agents are based off of the 'monogon builder' Docker image defined within build/Dockerfile. A follow up CR will remove the leftover of Phabricator CI machinery and explicitly document how that agent image is built and used. We also reformat a generated .bzl file to remove a spurious copyright header. This appeases Gazelle/Fietsje checks. Finally, we add a .gitignore which ignores build files to make the Gazelle/Fietsje dirty checkout detection work correctly. The internal version of the metropolis repository had an equivalent .gitignore which wasn't carried over during the initial migration into the Monogon monorepo. Change-Id: Ib88b8b50dbc6fcd034757558697e6ae2334235b1 Reviewed-on: https://review.monogon.dev/c/monogon/+/26 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 //...