Travis and github does not seem to be connected anymore

Travis CI Discussions & Feedback
1

Hi there,

We’re using travis ci pro connected to github.

Yesterday I added a new repository to our github, setup the .travis.yml as usual and my repository did not showed up on travis-ci.com.
When I try forcing the repository on travis, I end up with the following message:
This is not an active repository

When I click on the CTA (activate the repository on github) I end up on github organization page where the “All” option is selected…

I tried numerous things including:

  • Switch from all to specific and pick up the repository
  • Suspend / unsuspend the integration with travis
  • Uninstall/reinstall the travis app

Nothing worked and now it’s even worst, the app is installed but no builds are triggering for no repo at all on travis and we can’t trigger build manually.

This is a nightmare and support is not able to help solve the issue.

I tried manually adding a webhook to travis for some repos without success.

Nothing is working at all.

Thanks

3 Likes
2

Did this resolve for you? It seems like we are experiencing the same issue. We’re stuck.

1 Like
3

Hey Folks,

Can you please:

  1. Uninstall the Travis CI app for the User/Org by heading over to: GitHub Apps - Travis CI · GitHub and clicking on Configure(for the User/Org account)
  2. Reinstall the Travis CI app for the User/Org by heading over to: GitHub Apps - Travis CI · GitHub and clicking on Configure(for the User/Org account)
  3. Head over to app.travis-ci.com and Sync your account.
  4. Trigger a build on push commit and see if the issue is resolved.

Best,

1 Like
4

Hi @jexe,

Are you still stuck?

1 Like
5

Unfortunately, this still isn’t working for us. I followed the instructions above and no repositories are showing up. After removing access and granting access to the repository, I get the “Keep your hard hat on” page, and the repository is left unlinked, even after running Sync.

Let me know how I can help debug.

1 Like
6

Update: I was able to de-auth, and re-auth in a private browser, and things started working perfectly in the private browser for me – so that resolved things. I think something about my account was stuck in a bad state.

1 Like