-
Suggestion
-
Resolution: Unresolved
-
None
Summary:
Currently pipelines doesn't run deployment steps if they are restricted on certain branches when a tag is pushed if a branch restriction is applied on deployments.
Steps to reproduce:
- Configured pipelines to trigger on a tag and execute steps as below.
tags:
dvsc-*:
- step:
name: Deploytest
deployment: Staging
script:
- echo "Test in tags"
- Restricted deployments on staging to be run only from "master" branch using this feature in pipelines under repository settings.
Branches allowed to deploy to Staging:
- Pushed a tag to the repository
$ git tag -a dvsc-112 $ git push --tags Enumerating objects: 1, done. Counting objects: 100% (1/1), done. Writing objects: 100% (1/1), 167 bytes | 167.00 KiB/s, done. Total 1 (delta 0), reused 0 (delta 0) * [new tag] dvsc-112 -> dvsc-112
Pipelines was triggered on the above repository but it was failed with below message
Paused This pipeline was paused because Staging can only be deployed to from permitted branch pipelines.
It was paused because only pushes to master branch are allowed to deploy on staging environment.
Proposal:
Ability to enter tags and tag prefixes along with branches in the below screenshot should help running deployments using tags.