Reject deployment

[Dmitriy Kagarlickij]

I have added `trigger: manual` to my Deployment to manually check Build results before running deploy

In BitBucket UI I can only see `Deploy` button, but what if I want to reject it - how could it be done? 

Thanks!

[Theodora Boudale · Accepted solution]

Hi Dmitriy,

There is no option to reject or skip a manual step. We have a feature request for the ability to skip steps that you can vote for and watch here:

• https://jira.atlassian.com/browse/BCLOUD-20833

Do you have additional steps, after the deployment one, that you want to run?

Kind regards,
Theodora

[Dmitriy Kagarlickij]

No, I don't have any post-deploy steps, but I could add one if it helps to Reject deploy somehow

[Theodora Boudale]

Hi Dmitriy,

Adding post-deploy steps will not help with rejecting the deployment, I just asked to better understand your use case. Steps in a Pipelines build get executed sequentially at the moment; a common reason why users ask for the ability to skip a step, is so that they can skip for example the second step and execute a third one. This is what the feature request I shared is about.

Since there no other steps after the deployment one, you could ignore the deploy step and not run it. Could you please explain why you would like a reject option? What value would it add?

Kind regards,
Theodora

[Dmitriy Kagarlickij]

I see, thanks for clarification

I need to be able to Reject previous deploy if newer deploy was done (prevent human mistake)

[Theodora Boudale]

Hi Dmitriy,

Thank you for the feedback. I created a feature request for what you are asking in our issue tracker:

• https://jira.atlassian.com/browse/BCLOUD-23416

I suggest adding your vote to that feature request (by selecting the Vote for this issue link) as the number of votes helps the product managers better understand the demand for new features. You are more than welcome to leave feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to be notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request.

In the meantime, one option I could think of is deployment permissions:

• https://bitbucket.org/blog/deployment-permissions-now-available-in-bitbucket-pipelines

Deployment permissions are available on the Premium plan and you can use them to allow only admins to deploy to an environment. This won't allow you to reject a deployment, but it will prevent users who are not admins from running deployments.

Kind regards,
Theodora