Deployment permission when deploying on tag creation

[Gian Mario Contessa]

Hi, 

my CI/CD pypeline is configured with the following:

• PR creation
  1. run tests
• PR merge in "main" branch
  1. run tests
  2. deploy in dev
  3. manual trigger deploy in staging if desired
• TAG creation
  • manual trigger deploy in staging
  • manual trigger deploy in pre-prod and then prod environment

I set up each environment in the deployment section.

I restricted "main" branch write access to admins only

I restricted the pre-prod and prod environment to run only from "main" and if triggered by Admins

The problem:

Tagging causes the deployment on pre-prod and prod to fail (see image below)

Tags are on commits and I made sure to tag a commit in the "main" branch:

Why does Bitbucket throw this error?

[Theodora Boudale]

Hi Gian Mario and welcome to the community!

When deployments are restricted to certain branches only, then a tag will not run a deployment.

We have a feature request for the ability to specify tags allowed to deploy (along with branches):

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

I see that you already left a comment in that request. If you haven't done so already, please add your vote as well by selecting the link Vote for this issue. You can also add yourself as a watcher (by selecting the link Start watching this issue) if you'd like to be notified via email on updates.

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

In the meantime, if the tag is always added to the last commit of the main branch, you could create a custom pipeline for this deployment and trigger it manually from the Pipelines page of the repo (button Run pipeline) on the main branch.

Kind regards,
Theodora