From f30c741cf4a690f6e725af95c97d6579d25dc0bd Mon Sep 17 00:00:00 2001 From: cinereal Date: Thu, 10 Jul 2025 16:28:40 +0200 Subject: [PATCH] describe CI/CD see D2.6 --- architecture-docs/architecture.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/architecture-docs/architecture.md b/architecture-docs/architecture.md index b9f541f..384781c 100644 --- a/architecture-docs/architecture.md +++ b/architecture-docs/architecture.md @@ -166,3 +166,8 @@ The data model design for the configuration front-end needed support the desired Whereas the core abstraction in Fediversity is a NixOS configuration module, a more full-fledged example architecture of the web host use-case we aim to support as part of our exploitation would be as follows, where virtual machines in question run Fediversity to offer our selected applications: ![](https://git.fediversity.eu/Fediversity/meta/raw/branch/main/architecture-docs/host-architecture.png) + +### CI / CD + +In our simplest set-up, continuous integration and continuous deployment pipelines are handled using Forgejo's [built-in runner](https://code.forgejo.org/forgejo/runner), with relevant secrets handled using [Forgejo secrets](https://forgejo.org/docs/latest/developer/secrets/). Jobs we handle using CI include linting, formatting, testing, and a periodic life-cycle management job to keep our dependencies up-to-date. +In a future iteration, we may make use of [Gerrit](https://gerrit.googlesource.com/) to better manage our review process for incoming merge requests.