Adding the integration test suite into the CI #491
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#491
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?
Following the docs, we have two types of tests:
Fast and slow. The slow ones deploy things to servers. It takes ~ 30 mins. The fast ones take < 10 mins. This all depends on network conditions and the server being used, but it's a rough guide for the time being.
I imagine we could run these tests once a night on a cron job? Or we could separate them out and run the fast ones twice a day? Something like this.
I don't know if we have a ticket already but this all hinges on when we can get a more powerful CI server /cc @cas
Integration the integration test suite into the CIto Adding the integration test suite into the CIAh, here's the server migration ticket: #387
/cc @p4u1
Duplicate: #584