New commits on GitHub not triggering builds
I tested with two different repos and when I push a new commit to GitHub, the build is not triggering.
Imgs:
Recent deliveries through webhook
History in appveyor project
Third-party apps access in GitHub Organization
Appveyor project
https://ci.appveyor.com/project/DaniloBarros/xamarin/history
GitHub Repo
https://github.com/meutest/xamarin
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
1 Posted by Ilya Finkelshte... on Mar 31, 2017 @ 09:08 PM
Could you please send us content of specific webhook which did not trigger build? Please feel free to mark conversation private if needed.
Ilya.
2 Posted by petrikvandervel... on Apr 02, 2017 @ 08:57 AM
I think I'm experiencing the same issue. The information is:
Github project: https://github.com/nbuildkit/nBuildKit.MsBuild
Appveyor project: https://ci.appveyor.com/project/pvandervelde/nbuildkit-msbuild
I created the Appveyor project through the Appveyor UI and the webhook was setup in Github so I assume all permissions are correct. The webhook fires correctly. The last one had the following headers:
And the following content
The response was a 204 with the following header
Retrying this event did (again) not result in a build on Appveyor. The original event took place on 2017-04-02 20:29:41 New Zealand time (UTC + 12 at the moment)
3 Posted by dan.b412 on Apr 02, 2017 @ 04:46 PM
Sorry for the delay.
The webhook received a 204 response, same as @petrikvandervelde.
Regarding the last delivery of the webhook (417c1300-164e-11e7-852b-4b58b4751ac1 2017-03-31 17:11:42).
The specific delivery are the following:
Headers:
Payload:
In the response tab:
Response 204
Headers:
Body:
4 Posted by Ilya Finkelshte... on Apr 04, 2017 @ 07:17 AM
@petrikvandervelde You have
skip_non_tags: true
setting here and that commit was not tag. Actually you also haveskip_tags: true
here so your build does not have a chance to be started in any case... I would recommend start with simple basic configuration and adding filtering commits one by one5 Posted by Ilya Finkelshte... on Apr 04, 2017 @ 07:28 AM
@dan.b412 it is the same problem here with
skip_non_tags: true
here and the same problem with alsoskip_tags: true
being set which effectively block builds.6 Posted by petrikvandervel... on Apr 04, 2017 @ 09:48 AM
Darn, that's what I get for copying the configuration file from the website and not reading properly. I shall correct it! Thanks for spotting that one.
7 Posted by dan.b412 on Apr 04, 2017 @ 12:45 PM
Thank you @Ilya Finkelshteyn.
Sorry, for my lack of attention. I corrected it and now its working just fine. Thank you very much.
8 Posted by Ilya Finkelshte... on Apr 04, 2017 @ 08:35 PM
Welcome :)
dan.b412 closed this discussion on Apr 10, 2017 @ 01:57 PM.