Testing backup/restore as part of CI #104
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#104
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?
We got a report that Wordpress restores, and possibly backups, and possibly all app backup/restores, are broken.
Attempting a backup/restore during our continuous integration test runs seems like it could steer us clear of future similar misery.
Wondering if this means finally making a move on an
abra-deploy
Drone plugin instead ofstack-ssh-deploy
(I think this was mentioned in a ticket but can't remember which one), which might involve adding back the abra functionality to run commands based on environment variables (i.e.abra app - deploy
withDOMAIN
andTYPE
set..) or deciding that's a lost cause, deleting it all, and makingabra-deploy
use a temporary.env
file.Related to #69
Nice. Let's map out the CI suite next co-working session!
#69 (comment)