search

forcedotcom / devops-center-feedback

61 stars 2 forks source link

Cancel a promotion/deploy #222

Open vishnuyadavalli opened 2 years ago

vishnuyadavalli commented 2 years ago

Describe the bug When we start a deployment through DevOps center, and go to Deployment status page of the destination org and cancel the deployment, Devops center is not recognizing that the Deployment failed. Instead, it is merging the branch and marking the deployment as successful.

To Reproduce Steps to reproduce the behavior:

  1. Start a deployment in devops center.
  2. Navigate to Deployment status page of Destination org.
  3. Cancel the Deployment.
  4. You will see that deployment is sucessfull.

Expected behavior Deployment should fail.

Screenshots image image image image

Additional context Add any other context about the problem here.

kfidelak94 commented 1 year ago

We've got it on our roadmap to support the ability to cancel a promotion from DevOps Center. We'll also look at having DevOps Center recognize a canceled deployment if it is canceled from outside DevOps Center as reported here.

kfidelak94 commented 1 year ago

This is being tracked as W-11899869.

qdmistry commented 5 months ago

Upvoting this

jgwehr commented 4 months ago

@kfidelak94 Perhaps a similar bug related to your comment "recognize a canceled deployment if it is canceled from outside DevOps Center"

Describe the bug After >40 minutes, the Deployment Center "Pipeline" page fails to report that the Deployment failed with a fatal error in Salesforce. It continues to spin with no apparent way to cancel/restart/sync. This prevents any next steps. "Activity History" tab also lacks this update.

To Reproduce

  1. Accidentally include deleted fields which only existed in the working environment (ie. DevOps center creates destructiveChanges.xml - which is a separate bug/concern)
  2. Manually merge the DevOps-created PR in Github
  3. Choose the "catch up" promotion option in the target Org in DevOps Center
  4. Wait for Deployment to cease

Expected behavior

  1. The Deployment will fail due to issues with destructiveChanges.xml
  2. DevOps center should report this Failure and enable standard next steps

Image