Uploaded image for project: 'Planet4'
  1. Planet4
  2. PLANET-5443

Provide a way of rolling back Staging to the previous release

    XporterXMLWordPrintable

    Details

    • Type: Task
    • Status: CLOSED
    • Priority: Should have
    • Resolution: Released
    • Affects Version/s: None
    • Fix Version/s: 2.39.1
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      Sprint #144
    • Section:
      CI/CD
    • Track:
      Development
    • Repositories:
      planet4-base-fork, planet4-builder

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                nroussos Nikos Roussos
                Reporter:
                nroussos Nikos Roussos
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: