App CI/CD test suite brainstorming #69
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#69
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea is: what kidn of tests do we perform for new versions of apps before adding them to the recipes catalogue in https://apps.coopcloud.tech? Any version that lands in this catalogue should be somewhat reliable so that people can have reliable upgrades.
https://ci-apps.yunohost.org/ci/ is interesting to look at.
For example, if you look at their last Nextcloud test:
They do a bunch of specific YunoHost things which we don't need to do.
What steps would be important for us?
App CI system brainstormingto App CI/CD test suite brainstormingLet's merge #104 into here.
We should test backup/restore in our CI/CD suite.
I don't think it's a conventional CI thing but letting an app run for some time and doing some requests every couple of seconds/minutes might also prove useful. I deployed nextcloud the other day and it crashed after i made some requests to it, because PHP-fpm didn't have enough worker procesess (or something along these lines). We might not be able to implement it yet because of lack of resources, but I'd say that's an option to consider at some point
Think we're doing fine with the current wave of recipe CI efforts and renewed automagic catalog generation. Any CD vibes that come out of this can come in a more focused issue.