# Push invalid .travis-ci.yml does not trigger build

**URL:** <https://travis-ci.community/t/push-invalid-travis-ci-yml-does-not-trigger-build/5720>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** bug\
**Created:** [October 29, 2019, 3:07pm UTC](https://travis-ci.community/t/push-invalid-travis-ci-yml-does-not-trigger-build/5720 "2019-10-29T15:07:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![igagis](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/igagis/32/2810_2.png) [@igagis](https://travis-ci.community/u/igagis)\
**Post date:** [October 29, 2019, 3:07pm UTC](https://travis-ci.community/t/push-invalid-travis-ci-yml-does-not-trigger-build/5720/1 "2019-10-29T15:07:28Z")

</div>

When pushing a commit with invalid `.travis-ci.yml` file the web interface does nothing, it does not create a new build in the build history. So nothing happens, and it is confusing. Previously it was creating a new build in the history and the build failed immediately with ‘invalid travis yaml’ message.

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [October 29, 2019, 10:50pm UTC](https://travis-ci.community/t/push-invalid-travis-ci-yml-does-not-trigger-build/5720/2 "2019-10-29T22:50:22Z")

</div>

> [@No feedback whatsoever on invalid YAML](https://travis-ci.community/t/no-feedback-whatsoever-on-invalid-yaml/5485):
>
> Starting with [this commit](https://github.com/RalfJung/miri-test-libstd/commit/e410c8eb112388f0a38528f51a1ef81b4e3634f7), Travis stopped reacting to pushes to my repository. There was no error message, no feedback, even in the GitHub Webhook settings the response for the hook seemed fine: Headers: Connection: keep-alive Content-Length: 2 Date: Wed, 16 Oct 2019 07:59:45 GMT Server: Cowboy Via: 1.1 vegur X-Content-Type-Options: nosniff Body: {} I tried disabling and re-enabling Travis integration, no look. It all was quite mysterious. Only after lots of failed attempts I realized that I…
