No new builds being triggered


#1

Hi all,

https://travis-ci.org/google/swiftshader appears to be stuck at a build from two weeks ago, while 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

#2

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

Thanks.


#3

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.


#4

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.


#5

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


#6

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.


#7

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

Thanks.


#8

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. 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 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


#9

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.