Plan branch auto-merge / push fails with authentication error
Asked by Rajul Vora:

Bamboo build works all the way so rest of stash / git integration works as far as clone / checkout is concerned.

But when Bamboo attempts the plan branch merge and push, I get the following error. I don't know what is running at 127.0.0.1:39399 where bamboo is trying to connect for a git server and why it fails authentication.

Push command error: Warning: Permanently added '\[127.0.0.1\]:39399' (RSA) to the list of known hosts. fatal: remote error: Not authenticated Please authenticate and try your request again. fatal: The remote end hung up unexpectedly

In the atlassian-bamboo.log:

2014-03-05 15:22:20,675 WARN \[AtlassianEvent::0-BAM::EVENTS:pool-3-thread-15\] \[ChainExecutionManagerImpl\] Exception during push: command /usr/bin/git push **ssh://0f041d59-7d1f-4429-8f16-e1b31c8dfac2@127.0.0.1:39399**/kon/kumo-one.git feature/KON-2-test-jira-bamboo-integration failed with code 128. Working directory was \[/opt/atlassian/bamboo-home/xml-data/build-dir/serverSide/KONE-K1CI1-10/mergeWorkspace\]., stderr:

Warning: Permanently added '\[127.0.0.1\]:39399' (RSA) to the list of known hosts.

fatal: remote error: Not authenticated

Please authenticate and try your request again.

fatal: The remote end hung up unexpectedly


Answers:
author: rsperafico
body: Hi Rajul,

In Bamboo, by selecting "*Source Code Checkout* " in your plan, Bamboo will checkout from your repository and add to the *remote.origin.url* property the following information:

```
remote.origin.url=file:///&lt;bamboo-home&gt;/xml-data/build-dir/_git-repositories-cache/cdb8458fd0ffa89a43202ab15c042155b41362c1
```

In can get this information by going to *\<bamboo-home\>/xml-data/build-dir/\<project-key\>-\<plan-key\>/* and running the following command in your *Command Prompt/Terminal*:

```
git config -l
```

In order to be able to push code to your repository by, the property *remote.origin.url* needs to be updated to the *http(s)/ssh* to your repository. You can acchieve that by creating a *Script task* and adding the following to it:

```
# remove remote.origin.url valuegit remote remove origin
```

```
# add remote.origin.url value# you can get this information from the clone information to your repositorygit remote add origin ssh://git@&lt;stash-domain&gt;:7999/&lt;project-key&gt;/&lt;repository&gt;.git
```

```
# create a new fileecho "Hello World" &gt; greeting.txt
```

```
# add filegit add greeting.txt
```

```
# commitgit commit -m "add greeting"
```

```
# push to the repositorygit push origin master
```

Kind regards,  
Rafael


author: Tiare Balbi Bonamini
body: I'm getting the same error with Bamboo 5.6.2 and Stash 3.4.0. The output of the command git config -l on the folder *\<bamboo-home\>/xml-data/build-dir/\<project-key\>-\<plan-key\>/* is the correct repository url.

comments: author: Tiare Balbi Bonamini
body: Problem solved: <https://jira.atlassian.com/browse/BAM-14949>


author: admin admin
body: We are getting the same problem. Were getting the error in Bamboo 5.4.2 connected to Stash 2.11.2 and thought upgrading to Bamboo 5.5.1 connected to Stash 2.11.2 via the new Stash Application link might solve the problem. It did NOT. Please advice.


author: Dani
body: I'm getting the same problem as Rajul.

Any clue?


Tags: bamboo-administration