Captain ignores webhooks while building

[olehermanse]

Captain ignores webhooks while building. This means that if you push to multiple projects with GitHub webhooks, or have set up one github repo to send multiple webhooks to different captain apps, it won't work, some apps will never be built.

When 2 webhooks are received (roughly) at the same time, the second one is ignored with a 200 response, and this body:

{"status":1000,"description":"An active build (app name) is in progress... please wait..."}

If applicable, content of captain-definition file:
https://github.com/olehermanse/dagensquiz/blob/master/captain-definition
(It doesn't matter, though)

Steps to reproduce the problem:

• Set up a GitHub repo for a captain app
• Create 2 captain apps with different domains
• Set up webhooks on pushes to master for both
• 1 App will update, the other won't.

Captain should queue builds for different captain apps, and also not return 200 when the webhook was not successful.

[chromonav]

This problem is particularly a headache for mono-repos. Because of this captain does not initiate build for second app.

[githubsaturn]

Done. This feature will be available in the next release. For now, it's available on edge image:
https://caprover.com/docs/troubleshooting.html#how-to-use-the-edge-version