Skip to content
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 CI: Authentication failed for git push to release-1.4 #1124

Closed
janetkuo opened this issue Aug 29, 2016 · 10 comments
Closed

Travis CI: Authentication failed for git push to release-1.4 #1124

janetkuo opened this issue Aug 29, 2016 · 10 comments

Comments

@janetkuo
Copy link
Member

janetkuo commented Aug 29, 2016

$ git config --global user.email ${GIT_EMAIL}
The command "git config --global user.email ${GIT_EMAIL}" exited with 1.
...
The command "git merge -s recursive -X theirs homebase/release-1.4 -m "Sync from homebase"" exited with 0.
$ git push
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:
  git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
  git config --global push.default simple
See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)
remote: Anonymous access to kubernetes-v1-4/kubernetes-v1-4.github.io.git denied.
fatal: Authentication failed for 'https://:@github.com/kubernetes-v1-4/kubernetes-v1-4.github.io.git/'
The command "git push" exited with 128.
@janetkuo
Copy link
Member Author

cc @pwittrock

@janetkuo
Copy link
Member Author

@janetkuo
Copy link
Member Author

janetkuo commented Aug 31, 2016

I believe I've fixed it. Travis is now passing in newer PRs merged into release-1.4, see #1128

But old PRs are still using old travis configs...

@janetkuo
Copy link
Member Author

@jaredbhatti maybe know the answer?

@janetkuo
Copy link
Member Author

It seems that it passed just because I commited #1128 with GitHub :/

@janetkuo
Copy link
Member Author

@jaredbhatti it seems that people submitting PRs to release-1.4 need to send their git credential to travis env.global.secure to make travis pass?

@janetkuo
Copy link
Member Author

janetkuo commented Aug 31, 2016

In the failed travis build log, the following steps are missing

environment variables from repository settings
$ export encrypted_b7b6a058a6f4_key=[secure]
$ export encrypted_b7b6a058a6f4_iv=[secure]
Setting environment variables from .travis.yml
$ export GIT_EMAIL=[secure]
$ export GIT_NAME=[secure]
$ export GIT_USERNAME=[secure]
$ export GH_TOKEN=[secure]

@janetkuo
Copy link
Member Author

I found the root cause travis-ci/travis-ci#1500 (comment):

Secure environment variables are not included in pull request builds for security reasons. If they were, then anyone could submit a pull request and simply print out all the environment variables.

@jaredbhatti @pwittrock can we remove the travis script in release-1.4?

@janetkuo
Copy link
Member Author

I removed .travis.yml in release-1.4 branch

@jeffmendoza
Copy link
Contributor

looks like we are not using this any more

@jeffmendoza jeffmendoza removed their assignment Jan 10, 2017
mikutas pushed a commit to mikutas/k8s-website that referenced this issue Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants