rollback procedures

[wurstbrot]

needed to be added

[vbakke]

Rollback is an old procedure. And an activity that has varying degrees of maturity.. from 'well defined' (in a README) to 'automated'.

And some releases may not always have an easy rollback, even if the previous release in the same system had a really easy rollback. It all depends on what you changed, and how any database changes are "caught" after production goes live with a new (but not proper) release.

What sort of level should we set on this activity, @wurstbrot?

Rollback is definitely DevOps. But is it needed in DSOMM?

We could also mention 'rollback' in 'Defined deployemnt process' and (the new) 'Automated deployment process'?

[vbakke]

Just found the activity: 'Backup' (5c61fd6b-8106-4c68-ac28-a8a42f1c67dc).
I initially thought the 'Backup' activity was refering to regular backup or DB backup. However, reading this again, I see it is refering to backing up the artifact to be deployed. So that it is possible to roll back... 🙂

  risk:
    If errors are experienced during the deployment process you want to deploy
    an old release. However, due to changes in the database this is often unfeasible.
  measure:
    Performing automated periodical backups are used. Backup before deployment
    can help facilitate deployments whilst testing the backup restore processes.