Failed to connect to repository – 401 on Jenkins + Codebase Git

gitJenkins

I'm trying to get Jenkins to use Git as our SCM, and setting it up is being a bit of a pain.

When specifying the Codebase Git repo to use, using the following format:

https://our.domain.com/repository/repository.git

I get the following error from Jenkins:

Failed to connect to repository : Failed to connect to https://our.domain.com/repository/repository.git (status = 401)

The repository is private, and I'm not sure how to configure a user account for it. I've generated a RSA SSH key for the Jenkins user, on my Ubuntu server, and added this to Codebase as a deployment key.

I keep on getting the 404 error?

Also, if I try the

git@codebasehq.com:.../repository.git

format, I just get a different error from Jenkins:

Failed to connect to repository : Command "ls-remote -h git@codebasehq.com:.../repository.git HEAD" returned status code 128:
stdout: 
stderr: Host key verification failed. 
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Best Answer

I am late but In future this will help to other people

insted of

https://username@bitbucket.org/username/repo.git

replace this

https://bitbucket.org/username/repo.git

in the Git Repository URL

Related Solutions

Windows – Jenkins (Windows Service) with Git over SSH

I've been reading the following article, which is closely related: How do I tell Git for Windows where to find my private RSA key? and it gave a good hint: The HOME-Variable is crucial, but it didn't work out the way I thought.

After a lot of reasearch and trying I found this article: http://markashleybell.com/portable-git-windows-setting-home-environment-variable.html

In fact it is not enough to set the environment-variable in windows as usual, when running ssh from a service account, but change the configuration so the keys are actually found.

Short relevant outline:

Navigate to C:\Program Files\Git\etc\profile and add the following line

HOME="/c/Users/YourUserAccount"

before

# normalize HOME to unix path
HOME="$(cd "$HOME" ; pwd)"

This solved it for me, because now Git always uses your statically assigned path for home. Just make sure you don't get any security-issues with this approach with other users on this machine.

Git pull-push giving error

The issue is resolved. In mycase , it just worked out using the following url while cloning

http://username:password@localipaddress/git/project ,
instead of http://localipaddress/git/project.

May be some issue with the way username/pwds are handled by the repsoitory.

also in the .git/config file, need to check whether the following details are present

[remote "origin"]
    url = http://username:password@localipaddress/git/project 
    fetch = +refs/heads/*:refs/remotes/origin/*

[branch "master"]
    remote = origin
    merge = refs/heads/master

Related Topic