I've set my Appveyor build to release to GitHub when I push a
new tag, and I've set the release variable to
$APPVEYOR_REPO_TAG_NAME. But this seems to be set to
the same value as the "Build version format" in my repo config,
i.e. 1.0.{build}. This also results in a new tag being
pushed to GitHub, which triggers a new Appveyor build, in an
infinite loop.
Am I doing something wrong here? I just want to ensure that deploys either create a new GitHub release with my specified tag name, or update an existing release with new artifacts if Travis CI finishes first.
#1 Posted by Steph H on 06 Jun, 2016 01:55 PM
For reference, here's my
appveyor.yml:https://github.com/urschrei/lonlat_bng/blob/master/appveyor.yml
#2 Posted by Feodor Fitsner Support staff on 06 Jun, 2016 10:59 PM
http://help.appveyor.com/discussions/questions/1810-deployment-to-g...
Also, I'm not sure why would you need this: https://github.com/urschrei/lonlat_bng/blob/master/appveyor.yml#L6
#3 Posted by Steph H on 07 Jun, 2016 10:12 AM
Thanks Feodor, the branch regex fixed it. I had added the top-level
appveyor_repo_tag: truedirective because I wasn't sure where it was failing.Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:24 AM.