Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Plan branch auto-merge / push fails with authentication error

Rajul Vora March 5, 2014

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

4 answers

1 vote
rsperafico
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 18, 2014

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:///<bamboo-home>/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 value
git remote remove origin
# add remote.origin.url value
# you can get this information from the clone information to your repository
git remote add origin ssh://git@&lt;stash-domain&gt;:7999/&lt;project-key&gt;/&lt;repository&gt;.git
# create a new file
echo "Hello World" &gt; greeting.txt
# add file
git add greeting.txt
# commit
git commit -m "add greeting"
# push to the repository
git push origin master

Kind regards,
Rafael

0 votes
Tiare Balbi Bonamini November 10, 2014

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.

Tiare Balbi Bonamini November 10, 2014
0 votes
admin admin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 18, 2014

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.

0 votes
Dani April 3, 2014

I'm getting the same problem as Rajul.

Any clue?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events