-
Task
-
Resolution: Released
-
Should have
-
None
-
8
-
CI/CD
-
Sprint #144
When visual regressions tests fail on staging the deployment has already been done. If there is something to be fixed before promoting to production there is no easy way of testing it, since the second run will now show the differences.
Additionally it's good to have an easy way to rollback to a previous release in case of a big regression. This should be per instance, but also globally.
Tasks
- Use tags on base-fork to trigger release pipelines, so it's easier to rollback
- Add a rollback job to staging pipeline that promotes to production with the same tag
- Ideally everything should be done within CircleCI. Alternatively using a script.
- duplicates
-
PLANET-5408 Backstop reference image should also be the previous version when re-running the pipeline
- CLOSED
- is triggering
-
PLANET-5482 Provide a way of rolling back Production to the previous release
- CLOSED
- relates to
-
PLANET-5408 Backstop reference image should also be the previous version when re-running the pipeline
- CLOSED