Skip to content

Rollback command #23

@edudobay

Description

@edudobay

Depends on having a deployment log (#20).

Constraints:

  • Will yield an error if no previous deployment exists.
  • If the build for the previous deployment does not exist, we cannot do a strict rollback.
    • One possibility is to fail unless the --allow-rebuild option is given; then the build will be re-run against the original git commit.
    • We could instead fail and tell the user what they should do instead:

      Build for previous deployment is no longer available. If you want to rebuild it, run

      simple-git-deploy deploy --ref-name NAME_OF_PREVIOUS_REF \
        --ref COMMIT_REF` \
        --message "Rollback to new build for deployment DEPLOYMENT_ID"
      
    • If the original git commit does not exist anymore, this cannot succeed in any way.

Questions

  • Do we need to have special procedures for undoing a deployment?
    • I believe we can live without that; it probably would make our process too complex.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions