# No new builds being triggered

**URL:** <https://travis-ci.community/t/no-new-builds-being-triggered/185>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [September 26, 2018, 4:10am UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185 "2018-09-26T04:10:27Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![c0d1f1ed](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/c0d1f1ed/32/93_2.png) [@c0d1f1ed](https://travis-ci.community/u/c0d1f1ed)\
**Post date:** [September 26, 2018, 4:10am UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/1 "2018-09-26T04:10:27Z")

</div>

Hi all,

[https://travis-ci.org/google/swiftshader](https://travis-ci.org/google/swiftshader) appears to be stuck at a build from two weeks ago, while [https://github.com/google/swiftshader](https://github.com/google/swiftshader) contains many new commits.

I don’t see any indication of what might be wrong. Anyone got any clues?

Thanks!

- Nicolas

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [September 27, 2018, 2:43pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/2 "2018-09-27T14:43:03Z")

</div>

Hmm. The GitHub integration appears to be off. Could you try disabling and re-enabling Travis CI on this repo?

Thanks.

---

<div class="post-metadata">

**Author:** ![c0d1f1ed](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/c0d1f1ed/32/93_2.png) [@c0d1f1ed](https://travis-ci.community/u/c0d1f1ed)\
**Post date:** [September 27, 2018, 2:56pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/3 "2018-09-27T14:56:03Z")

</div>

Thanks for the feedback. I went to GitHub’s Settings \> Integration & services \> Manage Travis CI, and clicked the Test service button. A new build has now been triggered on Travis CI. So let’s see if it also keeps doing so for new pushes.

---

<div class="post-metadata">

**Author:** ![c0d1f1ed](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/c0d1f1ed/32/93_2.png) [@c0d1f1ed](https://travis-ci.community/u/c0d1f1ed)\
**Post date:** [September 27, 2018, 5:18pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/4 "2018-09-27T17:18:58Z")

</div>

Looks like it’s still not triggering builds on new pushes.

I tried unchecking Active in the GitHub’s Manage Travis CI page, but it gave me an error: “There was an error updating your hook: These events are not allowed for this hook: membership”

Then I noticed the note: “GitHub Services are being deprecated. Please contact your integrator for more information on how to migrate or replace a service with webhooks or GitHub Apps.”

I’ll look into those alternatives.

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [September 27, 2018, 7:19pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/5 "2018-09-27T19:19:05Z")

</div>

We have GitHub Apps integration out, so you might want to try that first.

---

<div class="post-metadata">

**Author:** ![c0d1f1ed](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/c0d1f1ed/32/93_2.png) [@c0d1f1ed](https://travis-ci.community/u/c0d1f1ed)\
**Post date:** [September 28, 2018, 3:16pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/6 "2018-09-28T15:16:03Z")

</div>

Google’s policy does not allow the GitHub Apps integration, because it requires write priviliges that we can’t grant for security reasons. I’ve reached out to our open-source support team to find another way to re-enable Travis CI.

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [September 28, 2018, 7:57pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/7 "2018-09-28T19:57:44Z")

</div>

I tried re-enabling the hook on our side, and it seems to have worked. Could you try pushing a new commit?

Thanks.

---

<div class="post-metadata">

**Author:** ![josh](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/josh/32/12_2.png) [@josh](https://travis-ci.community/u/josh)\
**Post date:** [September 28, 2018, 10:52pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/8 "2018-09-28T22:52:00Z")

</div>

Hi @c0d1f1ed, thanks for the issue report.

This `membership` problem is related to a GitHub v3 API misunderstanding where we asked for `membership` events, but that event type does not exist. The best path forward (for future reference) would be to delete the service hook altogether and use our website to add the integration back.

As for GitHub Apps, that is the new integration type we use on [travis-ci.com](http://travis-ci.com). I would love to understand what you mean by `Google’s policy does not allow the GitHub Apps integration, because it requires write priviliges`

Our GitHub Apps integration does not ask for write permissions, but our [travis-ci.com](http://travis-ci.com) login does. This is something we will be addressing very shortly as we do not want write permissions, the less permissions the better.

If there is someone we can talk to at Google to have this clarified, we would love to be put in touch.

Thanks a bundle

Josh

---

<div class="post-metadata">

**Author:** ![c0d1f1ed](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/c0d1f1ed/32/93_2.png) [@c0d1f1ed](https://travis-ci.community/u/c0d1f1ed)\
**Post date:** [October 4, 2018, 2:55am UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/9 "2018-10-04T02:55:09Z")

</div>

Hi @josh, I’ll try to get the full rationale from our GitHub integration support team and see if we can make things work with the GitHub Apps approach.

---

<div class="post-metadata">

**Author:** ![danielquinn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/danielquinn/32/853_2.png) [@danielquinn](https://travis-ci.community/u/danielquinn)\
**Post date:** [December 30, 2018, 2:34pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/10 "2018-12-30T14:34:32Z")

</div>

I can tell answer @josh’s question: Your site has a great big green button for integrating your Github account with Travis, that when you click it, demands write permission to all public & private repositories. I would never allow for that, so I’m here digging around your forum trying to figure out if there’s a workaround.

---

<div class="post-metadata">

**Author:** ![MelodicCrypter](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/melodiccrypter/32/2579_2.png) [@MelodicCrypter](https://travis-ci.community/u/MelodicCrypter)\
**Post date:** [August 22, 2019, 11:18am UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/11 "2019-08-22T11:18:40Z")

</div>

Hi, I am facing the same problem that @c0d1f1ed experienced before.

Previous 50 commits, all successfully triggered Travis to build. But, just today Travis is not building anymore after commits. This is my repo [EWWB](https://github.com/MelodicCrypter/Express-Workbox-Webpack-Babel-Scaffold). I can manually trigger build inside Travis, but git commits won’t trigger Travis anymore.

---

<div class="post-metadata">

**Author:** ![MelodicCrypter](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/melodiccrypter/32/2579_2.png) [@MelodicCrypter](https://travis-ci.community/u/MelodicCrypter)\
**Post date:** [August 22, 2019, 11:32am UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/12 "2019-08-22T11:32:31Z")

</div>

Don’t know what happened, but it’s triggering now. After **manually** triggering about 5 times, and I also tried to edit the .travis.yml (cause that’s what I’ve read maybe the indention, etc), it is now working again. Really don’t know the root cause though.

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [August 22, 2019, 12:27pm UTC](https://travis-ci.community/t/no-new-builds-being-triggered/185/13 "2019-08-22T12:27:50Z")

</div>

@MelodicCrypter you had a lot of jobs being queued, and additional ones had to wait.
