[scenario] testing upgrade and rollback scenarios
Some questions about upgrade/rollback workflows
If you have different opinions about what is required to be implemented for now and what could be required later -- please share such details.
Here are the list of points why upgrade/rollback scenarios should be done before other features:
- it's a kind of separate test-suite (set of test cases) and thus gives practice and ideas for custom test structure
- it's a suitable time to check various gpg-signature related workflows and thus gives ideas for pipeline jobs redesign
- it should run tests over the previously built image and thus gives ideas and constraints for pipeline storage redesign
Todos
Actionable items required for this issue to be resolved:
-
Explore and decide how to handle overall yield artifacts (#33 (comment 5622)) -
Job-structure / responsibility of (upgrade) check job(s) (#33 (comment 5621)) -
Documented findings and knowledge (#33 (comment 5617))