fossasia/gci16.fossasia.org

danger breaking Travis builds

Closed this issue · 2 comments

The following appears in all recent builds since #887:

$ if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then gem install danger; fi
Fetching: claide-1.0.1.gem (100%)
Successfully installed claide-1.0.1
Fetching: nap-1.1.0.gem (100%)
Successfully installed nap-1.1.0
Fetching: cork-0.2.0.gem (100%)
Successfully installed cork-0.2.0
Fetching: open4-1.3.4.gem (100%)
Successfully installed open4-1.3.4
Fetching: claide-plugins-0.9.2.gem (100%)
Successfully installed claide-plugins-0.9.2
Fetching: git-1.3.0.gem (100%)
Successfully installed git-1.3.0
Fetching: faraday-http-cache-1.3.1.gem (100%)
Successfully installed faraday-http-cache-1.3.1
Fetching: kramdown-1.13.2.gem (100%)
Successfully installed kramdown-1.13.2
Fetching: unicode-display_width-1.1.2.gem (100%)
Successfully installed unicode-display_width-1.1.2
Fetching: terminal-table-1.7.3.gem (100%)
Successfully installed terminal-table-1.7.3
Fetching: danger-4.0.4.gem (100%)
Successfully installed danger-4.0.4
11 gems installed
1.23s$ if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then danger --verbose; fi
Could not set up API to Code Review site for Danger

For your GitHub repo, you need to expose: DANGER_GITHUB_API_TOKEN

You may also need: DANGER_GITHUB_HOST, DANGER_GITHUB_API_BASE_URL

Found these keys in your ENV: MANPATH, XDG_SESSION_ID, rvm_bin_path, MYSQL_UNIX_PORT, GEM_HOME, TRAVIS_STACK_JOB_BOARD_REGISTER, HAS_JOSH_K_SEAL_OF_APPROVAL, NVM_CD_FLAGS, TRAVIS_STACK_LANGUAGES, SHELL, TERM, HISTSIZE, IRBRC, rvm_binary_flag, ELIXIR_VERSION, DERBY_HOME, SSH_CLIENT, TRAVIS_COMMIT, NVM_PATH, TRAVIS_OS_NAME, CASHER_DIR, OLDPWD, MY_RUBY_HOME, SSH_TTY, rvm_autoupdate_flag, LC_ALL, MIX_ARCHIVES, HISTFILESIZE, NVM_DIR, USER, rvm_remote_server_url4, _system_type, TRAVIS_LANGUAGE, PERLBREW_BASHRC_VERSION, rvm_path, TRAVIS, TRAVIS_REPO_SLUG, HAS_ANTARES_THREE_LITTLE_FRONZIES_BADGE, PYTHON_CONFIGURE_OPTS, TRAVIS_PULL_REQUEST, PAGER, VIRTUAL_ENV_DISABLE_PROMPT, RACK_ENV, rvm_gem_options, PERLBREW_ROOT, TRAVIS_STACK_TIMESTAMP, rvm_prefix, PYTHON_CFLAGS, PATH, MAIL, TRAVIS_PULL_REQUEST_SHA, TRAVIS_RUBY_VERSION, NVM_NODEJS_ORG_MIRROR, PWD, JAVA_HOME, CONTINUOUS_INTEGRATION, LANG, rvm_remote_server_verify_downloads4, TZ, MERB_ENV, _system_arch, PERLBREW_HOME, PS1, _system_version, TRAVIS_SUDO, TRAVIS_TAG, RBENV_SHELL, HISTCONTROL, rvm_version, TRAVIS_JOB_NUMBER, TRAVIS_EVENT_TYPE, PYENV_SHELL, PS4, HOME, SHLVL, BUNDLE_GEMFILE, GOROOT, RAILS_ENV, CI, rvm_remote_server_type4, TRAVIS_BUILD_ID, LOGNAME, TRAVIS_STACK_FEATURES, GEM_PATH, COMPOSER_NO_INTERACTION, J2SDKDIR, SSH_CONNECTION, LC_CTYPE, TRAVIS_SECURE_ENV_VARS, DEBIAN_FRONTEND, GOPATH, TRAVIS_STACK_NODE_ATTRIBUTES, NVM_BIN, TRAVIS_STACK_NAME, NVM_IOJS_ORG_MIRROR, GIT_ASKPASS, TRAVIS_BRANCH, XDG_RUNTIME_DIR, TRAVIS_COMMIT_RANGE, JDK_SWITCHER_DEFAULT, JRUBY_OPTS, TRAVIS_PULL_REQUEST_BRANCH, J2REDIR, TRAVIS_JOB_ID, RUBY_VERSION, _system_name, TRAVIS_BUILD_DIR, TRAVIS_BUILD_NUMBER, rvm_silence_path_mismatch_check_flag, _, BUNDLER_ORIG_PATH, BUNDLER_ORIG_GEM_PATH.

Failing the build, Danger cannot run without API access.

You can see more information at http://danger.systems/guides/getting_started.html

The command "if [ "$TRAVIS_PULL_REQUEST" != "false" ]; then danger --verbose; fi" exited with 1.

The easy way to 'fix' the travis build is to remove danger, but the real solution is to create a github api token for danger to use and put it into the environment variable DANGER_GITHUB_API_TOKEN.

The real fix can only be done by someone with access to the repository security settings.

Fixed it. Should work now.