Hi Greg,
To set up tag builds, you don't need to specify the branch the tag is from.
So you can set up a tag build off of 1.2.3-rc.1 like this, for example:
pipelines:
tags:
'*.*.*-rc.*':
- step:
script:
- echo "My tag build"
You should also be able to shorten this if you're just interested in release candidate builds:
pipelines:
tags:
'*rc*':
- step:
script:
- echo "My tag build"
A tag pipeline will only be triggered when a new tag is pushed (and matches an existing pipeline definition).
Thanks,
Phil
About this, i have commits to master with tags, those should go to pipeline and build, but if the commit even with tags goes to "staging" branch, then this would be accepted as "master" build. This is the issue.
Is there a way to say "Pipeline trigger with Tag on branch master only" ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi There,
I have this pipeline config as follow:
image: php:7.0.31
pipelines:
tags:
release-*:
-step:
name: Rebuild and release
script:
- #do something
And I get the following error: "The 'release-*' section in your bitbucket-pipelines.yml file must be a list."
May I please ask how to resolve this?
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have to put the tag-pattern into single quotes like:
'release-*'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.