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
Unable to authenticate with private Github repo - fails build every time #103
Comments
I got this to work by creating a docker image that had a credential stored on the disk at ~/.git-credential. I also set
Replace with an Github OAuth Token. See https://help.github.com/articles/git-automation-with-oauth-tokens/ This could also be fixed if the git clone command contained the token:password like this:
However, it would require a code change to make this happen by default. You COULD change the Github project url to include the credentials for each project but that's cumbersome. |
Following this, as I would like to use dotCI with our private repos 👍 |
Just a correction to @joeandaverde 's temporary solution with a |
@suryagaddipati I'm stuck on solving for this issue. Just wanted to +1 this as an issue for myself as well. |
Same issue here. |
Same issue here with trying to load a private repo as a git submodule. |
Private repos now work in |
The Github client is prompting for username when trying to clone private repo. It fails with:
I have provided client access key and authorized the application to have access to private repos through OAuth.
Jenkins ver. 1.595
May be related to #102
The text was updated successfully, but these errors were encountered: