Release to GitHub causes additional build
It appears that when I automatically release artifacts to GitHub the tagging/release process is kicking off the webhook to trigger an additional build on Appveyor.
Example:
Current at version 1 (Build #1).
Commit "readme.md" and push (Build #2)
Gets tagged a release 2 and artifacts release (Build #2)
An additional build is triggered, but not a release on GH (Build #3)
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 10 Feb, 2015 05:04 PM
Hi Matt,
On General tab of project settings set "Do not build on tags" or in appveyor.yml:
skip_tags: true
-Feodor
2 Posted by Matt Calhoun on 10 Feb, 2015 07:06 PM
Thanks again for the quick response! That did it! :)
~Matt
3 Posted by John B. on 23 Mar, 2015 01:41 AM
I think this bit me, too. I logged in today and there were something like thirty releases I had to delete from GitHub, and thirty tags to delete separately. I thought I kicked off a single build and went to bed. Thank goodness I checked on it before longer.
Please disallow the infinite build/release loop in AppVeyor. Nobody wants to do that on purpose.
4 Posted by ericnewton76 on 27 Dec, 2017 09:37 PM
So this just bit me just now, https://ci.appveyor.com/project/EricNewton/gmaps-api-net/history
I caught it about 4 releases in. In theory, AppVeyor should ignore a tag that AppVeyor created in the first place... =)
For instance, AppVeyor knows it created tag "v0.19.165" so the webhook from github to build "v0.19.165" should be ignored.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:25 AM.