Confusing behavior for the new Github apps integration

[stof]

When migrating an account to the new Github apps integration, repos which did not have a Travis configuration before started to be built as well (while Travis was not enabled on them), and were of course failing, as these were not ruby repos at all.
This is quite confusing. What is the recommended way to setup the Github Apps integration to avoid such behavior ?

[markduffield]

It would be nice if the integration settings allowed for some 'Global settings' to disable building for repos if a .travis.yaml file is not present.

[stof]

yeah, that would be fine with me

[BanzaiMan]

Hi, everyone. Sorry for the issue. We are aware of the issue, and we are tracking it. We hope to have updates soon.

[chris48s]

I am also affected by this. I think someone in our organisation activated the new integration and now we have builds unexpectedly trying to run on some repos. Is there a way I can manually disable them while this issue is open?

[hopewm]

@chris48s I was able to manually disable this on a per-repo basis via the "Build only if .travis.yml is present" toggle on the Settings tab at https://travis-ci.com/<your-org>/<your-repo>/settings.

For orgs with lots of repos, the global setting @markduffield suggested would be incredibly useful. 👍

[ritwickdey]

I'm facing same issue. I don't want any CI for few repo. But I can't turn off it.

Build only if .travis.yml is present is also not working for me.

I've checked the network tab. The request is being completed even.

[ndarville]

It’s been quite a week with Travis CI. All builds failed, then builds began to run for projects that were never added, now all my private repos aren’t listed anywhere.

If someone knows what to do about the latter, by all means let me know.

[BanzaiMan]

@ndarville Sorry to hear about the issue. Could you email support@travis-ci.com with details about your repository visibility issue? Thank you!

[stof]

@BanzaiMan on my side, I fixed the issue by applying the github app only to some specific repos rather than the whole organization on the github side.

I think this is related to the fact that Travis was enabling itself on a repo based on the webhook presence (as soon as it receives events, it runs builds). With org-level webhooks for github apps, this requires another opt-in system in Travis.

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[leonardodino]

@BanzaiMan is this issue fixed?

[stof]

I think https://changelog.travis-ci.com/all-builds-require-a-travis-yml-63545 fixed this