App CI/CD test suite brainstorming #69
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
1 Participants
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?
Following coop-cloud/abra#125. We'll be in a position to take on one part of what we discussed in the CoS fund - the apps CI system.
We have
renovate-bot
auto-merging upgrades anddrone-abra
auto-publishing new tags for us, the next is to run each app through a test suite like Yunohost does so that we can have some guarantee the new version can be deployed and will succeed.That test suite can have tests like, can you upgrade from the first version ever published all the way through to the last version without seeing a failure? Can you rollback the opposite way and not see a failure? Can you back up the app? And so on.
Hopefully from those suite builds we could generate a rating / score / etc. which could be the top-level thing other co-op cloud instance admins and end-users see.
Let's get the thoughts going in this thread anyway 🚀
Also depends on coop-cloud/abra#165.
App CI system brainstormingto App CI/CD test suite brainstorming