Builds not triggering from GitHub commit

Marco Craveiro's Avatar

Marco Craveiro

16 Oct, 2018 09:07 AM

Hi AppVeyor support,

Many thanks for providing an invaluable service to the open source and free software community. For some reason, my project in AppVeyor [1] stopped building yesterday; committing to github no longer triggers a new build. Now, I have been working on infrastructure over the last week and as a result I've triggered quite a few builds, so I'm not sure if I've hit some kind of internal limit. If so please let me know when it will be available again.

Many thanks for your time

Marco

[1] https://ci.appveyor.com/project/mcraveiro/dogen/history

  1. 1 Posted by Marco Craveiro on 16 Oct, 2018 10:12 AM

    Marco Craveiro's Avatar

    Actually, following on from the comments here [1], I checked my webhooks on github and for some reason they were "red". I deleted the webhook and recreated it. I then created a test commit. GitHub tells me AppVeyor is not happy:

    Cache-Control: no-cache
    Content-Length: 113
    Content-Type: application/json; charset=utf-8
    Date: Tue, 16 Oct 2018 10:11:01 GMT
    Expires: -1
    Pragma: no-cache
    Strict-Transport-Security: max-age=31536000
    X-Content-Type-Options: nosniff
    X-Frame-Options: SAMEORIGIN
    X-XSS-Protection: 1; mode=block
    Body
    {"message":"There was an error while trying to complete the current operation. Please contact AppVeyor support."}
    

    [1] https://help.appveyor.com/discussions/problems/6400-new-commits-on-...

  2. 2 Posted by Marco Craveiro on 16 Oct, 2018 10:13 AM

    Marco Craveiro's Avatar

    I also get this error if I try to trigger a manual build:

    There was an error while trying to complete the current operation. Please contact AppVeyor support.
    
  3. 3 Posted by Marco Craveiro on 16 Oct, 2018 11:21 AM

    Marco Craveiro's Avatar

    Aha, I think I found the problem by reading this discussion! [1] Not sure why it was all working yesterday though :-D Will try to move to the new way of doing things and report back.

    [1] https://help.appveyor.com/discussions/problems/17277-builds-do-not-...

  4. 4 Posted by Marco Craveiro on 16 Oct, 2018 11:34 AM

    Marco Craveiro's Avatar

    Ok right so I've deleted the webhook and checked my GitHub Applications. It sort of looks ok, though I can see two entries:

    AppVeyor 
    AppVeyor
    Last used within the last 2 weeks · Owned by appveyor
    
    AppVeyor CI 
    AppVeyor CI
    Last used within the last week · Owned by appveyor
    
  5. 5 Posted by Marco Craveiro on 16 Oct, 2018 02:21 PM

    Marco Craveiro's Avatar

    What I failed to mention on previous entry is that I still cannot build :-) Even triggering a build manually.

  6. 6 Posted by Marco Craveiro on 16 Oct, 2018 03:59 PM

    Marco Craveiro's Avatar

    This problem may be related to my account somehow; I have other projects in appveyor for which I also cannot manually trigger new builds: [1], [2].

    [1] https://ci.appveyor.com/project/mcraveiro/cpp-ref-impl [2] https://ci.appveyor.com/project/mcraveiro/csharp-ref-impl

  7. Support Staff 7 Posted by Ilya Finkelshte... on 16 Oct, 2018 04:16 PM

    Ilya Finkelshteyn's Avatar

    Hi Marco,

    You reached internal disk quota limit and your account was automatically blocked by abuse prevention system. We unblocked it, and increased your disk quota limit.

    However to stay on the safe side, you can also delete some folders with pre-installed software you do not need. For example rmdir C:\cygwin /s /q can give you a lot of space (if you do not need it). Another good candidate is C:\Qt (again if you do not need it).

    In any case you are good to go now.

    Ilya.

  8. 8 Posted by Marco Craveiro on 16 Oct, 2018 04:25 PM

    Marco Craveiro's Avatar

    Hi Ilya,

    thanks very much for the prompt response. Trying to understand how I did this :-) Is it because I triggered too many builds in one day? Otherwise, I didn't significantly change the way my application builds, I don't think; the gist of my changes of the last few days were:

    1. update to VS 2017
    2. use vcpkg instead of my own tarballs with dependencies - the sizes are similar
    3. use CTest to build rather than my own scripts.

    I guess my build log files are probably a lot bigger now because CTest logs on every test run but I think its probably a meg or two of difference... As you suggest, I don't really need either Cygwin or Qt so if this happens again I'll delete them, but I just want to make sure its not my application going mad and spewing lots and lots of random data! :-D

    Cheers

  9. 9 Posted by Marco Craveiro on 16 Oct, 2018 04:32 PM

    Marco Craveiro's Avatar

    Ah actually, the other thing I did over the last few days which was a tad unusual was cancelling a very large number of builds. As I was working on sorting my Travis infrastructure, a lot of the builds didn't add any value to Windows, so I cancelled them.

  10. 10 Posted by Marco Craveiro on 16 Oct, 2018 04:38 PM

    Marco Craveiro's Avatar

    Actually Ilya, I just committed to my repo and didn't automatically get a build for some reason. On the plus side, manually triggering a build now works, so that's great news :-) thanks a lot.

  11. 11 Posted by Marco Craveiro on 16 Oct, 2018 04:46 PM

    Marco Craveiro's Avatar

    Aha, it seems that the webhook is still required to trigger a build. I added it back again (I had removed it after reading this post [1]) and now the builds are triggering! I'm a happy camper again :-)

    thanks very much.

    [1] https://help.appveyor.com/discussions/problems/17277-builds-do-not-...

  12. Support Staff 12 Posted by Ilya Finkelshte... on 16 Oct, 2018 04:47 PM

    Ilya Finkelshteyn's Avatar

    OK, regarding the disk space issue. It seems that change to VS2017 is the reason. Visual Studio 2017 image has less free space. Not your fault at all. Many builds cannot affect this as each one starts on fresh VM.

    Regarding build not triggered, please check Events tab on the project level. We write a warning when AppVeyor skips a build for some reason. Let us know if you find it and if yes, does it explains the issue well.

    Side note. Do you know that we support Linux builds too?

  13. 13 Posted by Marco Craveiro on 16 Oct, 2018 07:04 PM

    Marco Craveiro's Avatar

    Ah, wasn't aware you had Linux builds as well! At present I'm happy enough with Travis but I'll keep that in mind.

    The builds seem to be working ok for now so I'll leave it as it is, any problems and I'll delete the folders you suggested. Thanks for all your help.

  14. Support Staff 14 Posted by Ilya Finkelshte... on 17 Oct, 2018 05:23 AM

    Ilya Finkelshteyn's Avatar

    Sure, ping us when needed.

  15. Ilya Finkelshteyn closed this discussion on 17 Oct, 2018 05:23 AM.

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