commit | a6a039209495ee74c2e830a55f496e901b6a3b5b | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@monogon.tech> | Mon Nov 13 19:57:48 2023 +0100 |
committer | Serge Bazanski <serge@monogon.tech> | Mon Nov 20 11:36:53 2023 +0000 |
tree | 11c915326c4b2c7b16dec2f67f595a3cb9a5db3b | |
parent | 79d0b0d518efef2f86904443b8612ed6bd90cb8c [diff] |
build: new workspace status script, new versioning scheme This reimplements the workspace status script and fixes a bunch of issues along the way: 1. The script is now in Python, which allows us to better express some complexity. 2. We now retrieve the Kubernetes version from third_party/go/repositories.bzl, thereby unhardcoding the Kubernetes version. 3. We now support for multiple 'products' with different versions. Currently we have only one product, which is metropolis. This is the basis for tying Git tags to releases of a particular codebase within the monorepo. 4. Git tags are now parsed to retrieve the version of a product, instead of it being hardcoded in the workspace status script. 5. We use a vX.Y.Z-devNNN versioning system for builds which have happened in between tags. NNN is the number of commits since vX.Y.Z. This changes the current version of Metropolis from 0.1 to 0.1.0-dev440. In an upcoming change we will implement a Go-side library to caputure information about the workspace state, both the per-repo data like VCS state and per-product data like versions. For now we keep a stopgap in the new script to emit version data as expected by the current codebase. Change-Id: I07cb17efc7d60aa269627a549f56ffa1bfdeb5b7 Reviewed-on: https://review.monogon.dev/c/monogon/+/2304 Reviewed-by: Lorenz Brun <lorenz@monogon.tech> Reviewed-by: Leopold Schabel <leo@monogon.tech> Tested-by: Jenkins CI Reviewed-by: Tim Windelschmidt <tim@monogon.tech>
This is the main repository containing the source code for the Monogon Platform.
This is pre-release software - take a look, and check back later!
Our build environment is self-contained and requires only minimal host dependencies:
/dev/kvm
(if you want to run tests).Our docs assume that Bazelisk is available as bazel
on your PATH.
Refer to SETUP.md for detailed instructions.
Build CLI and node image:
bazel build //metropolis/cli/dbg //:launch --config dbg
Launch an ephemeral test node:
bazel test //:launch --config dbg --test_output=streamed
Run a kubectl command while the test is running:
bazel-bin/metropolis/cli/dbg/dbg_/dbg kubectl describe node
Run full test suite:
bazel test --config dbg //...