Git tags appear both as new tags and new branches, limiting deploy restriction options
See for example this build:
https://ci.appveyor.com/project/hymerman/foo-bestversion/build/1.0.18
I pushed a new tag, '1.0.3'. AppVeyor shows this as both a new tag, and a new branch. There is no branch called '1.0.3'. Since I have deployment restricted to new tags on the 'master' branch, the log shows that the branch doesn't match and it doesn't run the deploy step.
Am I doing something wrong? I think I understand the AppVeyor side correctly; even the AppVeyor docs on deployment use new tags on master branch as their example:
- provider: Environment
name: production
on:
branch: master
appveyor_repo_tag: true
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 02 Jan, 2016 01:13 AM
If branch has the same name as tag then webhook payload didn't have the information about base branch. You can check webhook "Recent deliveries" on GitHub to see that.
2 Posted by Ben Hymers on 03 Jan, 2016 10:44 PM
Brilliant, thanks - I've looked at the data on GitHub's end and you're
right. In this case I pushed the tag before the commit, which may have
confused things, even though I later deleted then force pushed a new tag
with the same name to try to do it the right way round. I'll try pushing
the commit then the tags next time, sounds like that should work as
expected.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:03 AM.