App CI/CD test suite brainstorming #69

Closed
opened 2021-06-04 14:27:09 +00:00 by decentral1se · 3 comments
Owner

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:

https://ci-apps.yunohost.org/ci/job/3105

They do a bunch of specific YunoHost things which we don't need to do.

What steps would be important for us?

  • recipe repo linting
  • fresh install from scratch
  • removal of app
  • backing up
  • restoring from backup
  • upgrading
  • rolling back
  • ?
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: > https://ci-apps.yunohost.org/ci/job/3105 They do a bunch of specific YunoHost things which we don't need to do. What steps would be important for us? - recipe repo linting - fresh install from scratch - removal of app - backing up - restoring from backup - upgrading - rolling back - ?
decentral1se added this to the (deleted) milestone 2021-06-04 14:27:09 +00:00
decentral1se added the
enhancement
label 2021-06-04 14:27:09 +00:00
decentral1se changed title from App CI system brainstorming to App CI/CD test suite brainstorming 2021-06-04 14:28:45 +00:00
decentral1se added the
ci/cd
label 2021-06-17 20:18:18 +00:00
Author
Owner

Let's merge #104 into here.

We should test backup/restore in our CI/CD suite.

Let's merge https://git.coopcloud.tech/coop-cloud/organising/issues/104 into here. We should test backup/restore in our CI/CD suite.
decentral1se added this to the Versioning and deploy stability milestone 2021-09-09 14:29:50 +00:00
decentral1se modified the milestone from Versioning and deploy stability to Continuous integration testing for apps 2021-09-09 14:30:19 +00:00
Owner

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

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
decentral1se added this to the Beta release (software) project 2021-10-14 18:40:49 +00:00
decentral1se removed this from the Beta release (software) project 2021-12-21 23:27:28 +00:00
Author
Owner

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.

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.
Sign in to join this conversation.
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#69
No description provided.