automated dev-ops workflows #224

New issue

Open

opened 2025-03-03 16:36:13 +01:00 by kiara · 0 comments

kiara commented

2025-03-03 16:36:13 +01:00

Owner

As a developer working on Fediversity,
I want for development to use a quick yet comprehensive automated workflow maintaining, verifying and deploying our code,
so that I may iterate quickly and have an easy time contributing to the project.

dependencies

#770 cut dependence on deployment/check/'s extraTestScript
#33 get the Pixelfed tests to run in CI
#362 NixOS tests break when CI runs them in parallel
#704 tests' memory metadata
#560 in-source patches
#517 all tests exposed through flake
#29 Backups for Forgejo
#366 use dedicated Nix builder
#327 initial focus on single application for development
#279 unify versioning
#65 Automated dependency updates
#177 infrastructure automatically deployed using continuous deployment
#561 cache reusable computations
#567 split out CI checks to separate jobs
#721 tests use lightweight containers
#720 limit closure size
#277 Full integration test
#102 CI rejects failing deployments
#13 Beefier Forgejo actions machines
#302 code reviewers can suggest changes
#370 fediversity apps reused in infra
#199 derive users and their keys from the keys directory
#248 Nix package overlays upstreamed
#691 application testing coverage upstreamed
#69 Separate test environments for staging vs. production
#272 support password-protected personal SSH keys for deploying services in development
#93 Write all modules with destructured arguments
#314 ephemeral state is automatically provisioned
#529 avoid referencing parent directories
#372 refactor environment variables to typed django settings
#382 panel nix package allows declaring users
#383 panel allows specifying SSH key
#384 CA certificates in NixOS tests generated declaratively
#423 alleviate pain from tests requiring to manually specify extraDependencies
#774 development workflow based on interactive VMs
#467 Integration-tested progress reports
#643 block aggressive scrapers on forgejo
#377 Integration tests for MVP

**As** a [developer working on Fediversity](https://git.fediversity.eu/org/Fediversity/teams), **I want** for development to use a quick yet comprehensive automated workflow maintaining, verifying and deploying our code, **so that** I may iterate quickly and have an easy time contributing to the project. ### dependencies 1. #770 cut dependence on `deployment/check/`'s `extraTestScript` 1. #33 get the Pixelfed tests to run in CI 1. #362 NixOS tests break when CI runs them in parallel 1. #704 tests' memory metadata 1. #560 in-source patches 1. #517 all tests exposed through flake 1. #29 Backups for Forgejo 1. #366 use dedicated Nix builder 1. #327 initial focus on single application for development 1. #279 unify versioning 1. #65 Automated dependency updates 1. #177 infrastructure automatically deployed using continuous deployment 1. #561 cache reusable computations 1. #567 split out CI checks to separate jobs 1. #721 tests use lightweight containers 1. #720 limit closure size 1. #277 Full integration test 1. #102 CI rejects failing deployments 1. #13 Beefier Forgejo actions machines 1. #302 code reviewers can suggest changes 1. #370 fediversity apps reused in infra 1. #199 derive users and their keys from the keys directory 1. #248 Nix package overlays upstreamed 1. #691 application testing coverage upstreamed 1. #69 Separate test environments for staging vs. production 1. #272 support password-protected personal SSH keys for deploying services in development 1. #93 Write all modules with destructured arguments 1. #314 ephemeral state is automatically provisioned 1. #529 avoid referencing parent directories 1. #372 refactor environment variables to typed django settings 1. #382 panel nix package allows declaring users 1. #383 panel allows specifying SSH key 1. #384 CA certificates in NixOS tests generated declaratively 1. #423 alleviate pain from tests requiring to manually specify `extraDependencies` 1. #774 development workflow based on interactive VMs 1. #467 Integration-tested progress reports 1. #643 block aggressive scrapers on forgejo 1. #377 Integration tests for MVP