New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis says that the repo is not active, while this is wrong #5629

Closed
stof opened this Issue Feb 15, 2016 · 7 comments

Comments

Projects
None yet
4 participants
@stof

stof commented Feb 15, 2016

https://travis-ci.org/KnpLabs/KnpMenuBundle shows This is not an active repository, which is wrong. The repo has Travis enabled since years (and going to the list of builds still display builds properly)

@roidrage

This comment has been minimized.

Show comment
Hide comment
@roidrage

roidrage Feb 15, 2016

Member

If this repository is indeed still active, then it's likely it was enabled via manual configuration of the GitHub webhook in the GitHub settings for the repositories instead of enabling the hook on the Travis CI account.

This is easy to fix, you just need to go to the profile for KnpLabs and activate it manually. That should make the message disappear.

Member

roidrage commented Feb 15, 2016

If this repository is indeed still active, then it's likely it was enabled via manual configuration of the GitHub webhook in the GitHub settings for the repositories instead of enabling the hook on the Travis CI account.

This is easy to fix, you just need to go to the profile for KnpLabs and activate it manually. That should make the message disappear.

@stof

This comment has been minimized.

Show comment
Hide comment
@stof

stof Feb 15, 2016

Will it detect that the hook is already there or will it duplicate it ?

stof commented Feb 15, 2016

Will it detect that the hook is already there or will it duplicate it ?

@stof

This comment has been minimized.

Show comment
Hide comment
@stof

stof Feb 15, 2016

And it might be good to let people know about this change, as this is quite new. The fix is easy, but only once you know what is causing it.

stof commented Feb 15, 2016

And it might be good to let people know about this change, as this is quite new. The fix is easy, but only once you know what is causing it.

@roidrage

This comment has been minimized.

Show comment
Hide comment
@roidrage

roidrage Feb 15, 2016

Member

It should detect that the hook is already there assuming it was set up with the service Travis CI on GitHub rather than as a generic webhook.

This change was rolled out quite a few months ago (mid 2015 ish), and we've since been interacting with quite a few folks who've reported this, and haven't really had any further reported issues since.

Member

roidrage commented Feb 15, 2016

It should detect that the hook is already there assuming it was set up with the service Travis CI on GitHub rather than as a generic webhook.

This change was rolled out quite a few months ago (mid 2015 ish), and we've since been interacting with quite a few folks who've reported this, and haven't really had any further reported issues since.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Apr 6, 2016

FTR, we got bit by this at gratipay/gratipay.com#3988.

a quick google search shows many matching results. Can it because of this?

FTR, we got bit by this at gratipay/gratipay.com#3988.

a quick google search shows many matching results. Can it because of this?

@stakach

This comment has been minimized.

Show comment
Hide comment
@stakach

stakach Jun 27, 2016

This happened to me too. Even though the repository is active, I retro-actively added some tags for things that happened months ago and then travis deactivated.

stakach commented Jun 27, 2016

This happened to me too. Even though the repository is active, I retro-actively added some tags for things that happened months ago and then travis deactivated.

@stale

This comment has been minimized.

Show comment
Hide comment
@stale

stale bot Apr 14, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. 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

stale bot commented Apr 14, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. 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

@stale stale bot added the stale label Apr 14, 2018

@stale stale bot closed this Apr 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment