Allow Rollback in urgency with Prevent Outdated Deployment Job feature

Problem

With the recent improvement of Prevent Outdated Deployment Job feature (ex. "Skip Outdated Deployment Jobs"), users can't rollback to the previous/outdated deployment because it's invalidated by the latest deployment. This is expected behavior, however, there are some cases that urgent rollback is needed to restore the production status.

See Prevent outdated deployment jobs for more information.

Workarounds

Workaround 1: Temporarily disable the feature, rollback and re-enable.

• Visit Project > Settings > CI/CD > General Pipelines
• Check/Uncheck the Skip outdated deployment jobs checkbox (or Prevent outdated deployment jobs checkbox).
• Click Save changes.

Workaround 2: Run a new pipeline with previous commit.

• Visit Project > Repository > Branches
• Click New branch
• Fill the fields:
  • Branch name: Anything e.g. rollback-branch.
  • Create from: The previous commit SHA e.g. 17d0e95040ee55a5b329b6f45b3a0a890590d1e8.
• Click Create branch
• A new deployment pipeline runs, which contains newer deployment jobs than the latest deployment.

Proposal

Allow rollback if the job finished in the past.