travis.rb: Github Release setup fails

After using travis setup releases and entering the correct credentials 100 times I always get this error that suggests that there is a problem with Github two factor authentication.

BTW, the credentials I used are the correct ones. I just logged in with the same One Time Code aswell…

System
Ruby:                     Ruby 2.0.0-p451
Operating System:         Mac OS X 10.9.3
RubyGems:                 RubyGems 2.0.14

CLI
Version:                  1.6.11
Plugins:                  none
Auto-Completion:          yes
Last Version Check:       2014-06-08 12:24:23 +0200

Session
API Endpoint:             https://api.travis-ci.org/
Logged In:                no
Verify SSL:               yes
Enterprise:               no

Endpoints
org:                      https://api.travis-ci.org/ (current)

Last Exception
An error occurred running `travis setup --org`:
    RuntimeError: Validation Failed
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:206:in `rescue in login'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:195:in `login'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:204:in `rescue in login'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:195:in `login'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:74:in `possible_tokens'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:41:in `each_token'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/tools/github.rb:36:in `with_token'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/setup/releases.rb:12:in `block in run'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/setup/service.rb:61:in `block in deploy'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/setup/service.rb:52:in `configure'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/setup/service.rb:60:in `deploy'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/setup/releases.rb:11:in `run'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/setup.rb:47:in `run'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli/command.rb:181:in `execute'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/lib/travis/cli.rb:60:in `run'
        from /Library/Ruby/Gems/2.0.0/gems/travis-1.6.11/bin/travis:18:in `<top (required)>'
        from /usr/bin/travis:23:in `load'
        from /usr/bin/travis:23:in `<main>'

About this issue

Original URL
State: closed
Created 10 years ago
Comments: 17 (1 by maintainers)

Commits related to this issue

better description for generated GitHub token used for GitHub Releases, see #199 — committed to travis-ci/travis.rb by rkh 10 years ago

Most upvoted comments

I tried to follow @wclyffe 's answer, but it lacked a full URL in this statement:

I noticed that a new personal access token temporary token has been created on the settings/applications page

So, I assumed that settings/applications page meant: https://github.com/settings/applications

Unfortunately, it seems that the token settings have moved to another page on GitHub. Right now I have to go to this URL on github in order to see the tokens:

https://github.com/settings/tokens

So the current solution to this problem [1] is:

delete the existing token on https://github.com/settings/tokens
then rerun the travis setup releases command.

[1] This assumes you are in the same situation as me: regenerating the token for a GitHub project that already has a token listed in https://github.com/settings/tokens

erikdw on Jun 16, 2016

Same problem here… I noticed that a new personnal access token temporary token has been created on the settings/applications page on the first run of travis setup releases. If I delete that token before running travis setup releases again, it works.

I suppose this is the token used by travis for deployment. And if so, shouldn’t if be given a name more appropriate to give a hint of what it is used for? Or am I mistaken, the token being really temporary, and can be deleted?

wclyffe on Jun 19, 2014

Ditto, but @wclyffe’s solution doesn’t work, as I don’t have a temporary token…

patcon on Apr 27, 2015