Open matthewkmayer opened 7 years ago
@matthewkmayer could you please send specific time (with time zone) when webhook was sent? I want to check our traces. I am not sure how can I get exact time from here and it is pretty difficult to dig traces for long periods of time.
Sure thing! I redelivered the latest webhook Oct 7, 2017 10:10 AM Pacific time. I believe that's 10-07-2017 17:10 UTC.
Bump, I stumbled upon the same issue issue today. Last tag build that was built and deployed successfully was https://ci.appveyor.com/project/JustArchi/archisteamfarm/build/4645-master (3.0.3.4) yesterday. Today I created tag 3.0.3.5 and new build was not scheduled, I tried re-delivering webhook messages and also no go, finally I removed and pushed tag again generating new webhook message and that didn't work either. I didn't change any AppVeyor configuration bit since when it was working, it happened out of sudden. Normal commits are triggering build properly. Thank you.
I re-tagged my release at different point of time and it worked now.
It could be a coincidence, but my faulty tag had "merge branch" as last commit. In any case it works for me now.
Still seeing this. Here's my workflow:
master
branchv0.3.2
I expect the tag push to kick off a new Appveyor build that publishes the artifact back to Github. This workflow is successful with TravisCI.
Latest tag push event is around 17:12:00 UTC Saturday, October 28, 2017.
The merge commit to master is correctly built but it's missing the tag that isn't pushed yet. I see this in the merge build logs:
"GitHub" deployment has been skipped as environment variable has not matched ("appveyor_repo_tag" is "false", should be "true")
Let me know if I can provide more info! 😄
Are you sure you're tagging latest commit and not hitting this?
Just making sure because it's what was happening in my case, and your description is very similar.
Thanks for the help!
It looks to be the latest commit:
$ git fetch
$ git lg1
( from https://stackoverflow.com/questions/1057564/pretty-git-branch-graphs )
* 1c46684 - (20 minutes ago) Merge pull request #71 from matthewkmayer/update-deps-bump-version - Matthew Mayer (HEAD -> master, tag: v0.3.2, origin/master, origin/HEAD)
|\
| * a88f308 - (38 minutes ago) Update deps, bump to version 0.3.2. - Matthew Mayer (update-deps-bump-version)
|/
* 94e270a - (4 days ago) Merge pull request #68 from matthewkmayer/update-readme - Matthew Mayer
Looks good, then perhaps it's some other issue, always worth a try 🙂.
I'm working on publishing Windows versions of release-party and only want to do that for git tags.
It appears I've got some Appveyor settings telling it to skip tags, as I can create a tag, push to GitHub and a new build will not fire off. I see this in the build output when I re-run a build on the same commit but was caused by a push to the branch:
I see GitHub has delivered a webhook successfully to Appveyor with a 204 response code:
Resending the web hook doesn't make a build happen, so I figure it's something with how my project is configured. As far as I can tell my Appveyor config file is set up right but apparently not. I'd sure like a hand making this work! 😄