build/ci: add bazel mod tidy step

Running `bazel mod tidy` on the current main branch causes a change in
build/bazel/rust.MODULE.bazel. If `bazel run //:go -- mod tidy` changes
go.mod, it will also also run `bazel mod tidy`, which means that this
will eventually be noticed in a later unrelated change. But it is better
if this is noticed and fixed immediately, so I added `bazel mod tidy` to
the steps run by CI. It looks like we then don't need `bazel mod deps`
anymore.

I also moved the git status step to the post always block, such that it
is run even if one of the previous steps fails. For example,
`bazel run //:gazelle -- update` can fail if a change to
MODULE.bazel.lock is necessary. This should make it easier to understand
why the pipeline failed, because you can then still see which files have
changed, and the "Unclean working directory" message is printed.
I tested that this works, and that the pipeline still fails if a step
in the always block fails.

Change-Id: I05e3f1a5d9e45ba16058cc6758b0acb106458cae
Reviewed-on: https://review.monogon.dev/c/monogon/+/3609
Tested-by: Jenkins CI
Reviewed-by: Tim Windelschmidt <tim@monogon.tech>
3 files changed
tree: 1f57a604f9f3e9420e8d7bde27d8ae5fed31ea98
  1. .github/
  2. build/
  3. cloud/
  4. go/
  5. intellij/
  6. metropolis/
  7. osbase/
  8. third_party/
  9. tools/
  10. version/
  11. .bazelignore
  12. .bazelproject
  13. .bazelrc
  14. .bazelrc.ci
  15. .bazelrc.sandboxroot
  16. .bazelversion
  17. .git-ignore-revs
  18. .gitignore
  19. BUILD.bazel
  20. CODING_STANDARDS.md
  21. go.mod
  22. go.sum
  23. LICENSE
  24. MODULE.bazel
  25. MODULE.bazel.lock
  26. README.md
  27. SETUP.md
  28. shell.nix
  29. WORKSPACE
README.md

Monogon Monorepo

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! In the meantime, join us on Matrix (#monogon-os-community:matrix.org) or Discord.

Environment

Our build environment is self-contained and requires only minimal host dependencies:

  • A Linux machine or VM.
  • Bazelisk >= v1.15.0 (or a working Nix environment).
  • A reasonably recent kernel with user namespaces enabled.
  • Working KVM with access to /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.

Monogon OS

The source code lives in //metropolis (Metropolis is the codename of Monogon OS).

See the //metropolis/README.md for a developer quick start guide, or see the Monogon OS Handbook for user documentation.