flancian/docs.coopcloud.tech
0
0
Fork 0
forked from toolshed/docs.coopcloud.tech
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: wording on 022

Browse Source
This commit is contained in:
decentral1se
2024-04-05 00:02:59 +02:00
parent f0875a735a
commit ff39cf10b6
1 changed files with 10 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/federation/resolutions/in-progress/022.md
View File

@ -9,7 +9,9 @@ title: "Resolution 022"
### Summary ### Summary
Motivated by the collective release planning: [`#583`](https://git.coopcloud.tech/coop-cloud/organising/issues/583) under "Automate Integration Test Suite". Motivated by the collective release planning:
[`#583`](https://git.coopcloud.tech/coop-cloud/organising/issues/583) under
"Automate Integration Test Suite".
The latest `abra` release (`0.9.x`) was heavily delayed due to several issues. The latest `abra` release (`0.9.x`) was heavily delayed due to several issues.
One of those was the need to fix the integration test suite which wasn't run in One of those was the need to fix the integration test suite which wasn't run in
@ -26,12 +28,11 @@ slow, fast and only a few require public DNS. This means we can break up the
tests and run them in separate "builds" to speed things up. This involves some tests and run them in separate "builds" to speed things up. This involves some
research & experimentation. research & experimentation.
Also, we need a server to run the tests on. This machine should be wiped clean A server has been provided by `@mirsal` on donation (💘). This machine will be
each day (`docker <command> prune ....`) and have the usual DNS machinery be wiped clean each day (`docker <command> prune ....`) and will have the usual
attached to it, e.g. `int.coopcloud.tech`, `*.int.coopcloud.tech`. Ideally some DNS machinery attached to it, e.g. `int.coopcloud.tech`, `*.int.coopcloud.tech`.
federation members will also be provided shell access with root permissions.
Once all this is wired up, we can implement the CI/CD configuration to make the Once that is all wired up, we can implement the CI/CD configuration to make the
test suite run automatically once a day. This will be triggered via the test suite run automatically once a day. This will be triggered via the
`.drone.yml` in the `abra` Git repository. `.drone.yml` in the `abra` Git repository.
@ -40,10 +41,8 @@ Budget details:
| Item | Cost | Who? | | Item | Cost | Who? |
| ---- | ---- | ---- | | ---- | ---- | ---- |
| Server | Free (on donation) | `@mirsal` | | Server | Free (on donation) | `@mirsal` |
| Server setup & docs | 1 hrs | `@d1` | | Server setup & docs | 1 hour | `@d1` |
| R & D for breaking up tests | 5 hrs | `@d1` | | R & D for breaking up tests | 5 hours | `@d1` |
| Implementing CI/CD configs | 10 hrs | `@d1` | | Implementing CI/CD configs | 10 hours | `@d1` |
**Total: 16 hrs * 20 EUR = 320 EUR** **Total: 16 hrs * 20 EUR = 320 EUR**
Big thanks for `@mirsal` for donating the server 💘