Merge branch, push back merged result fails - Linux

All our plan branches which are set to merge using gatekeeper strategy fail the build with:

Push command error: Pushing to ssh://c90adc1b-f1d4-44e2-99fc-69ebe6e95208@127.0.0.1:47671/reponame/projectname.gitfatal: The remote end hung up unexpectedlyfatal: The remote end hung up unexpectedly

Everything else works fine.

(Linux)

9 answers

1 accepted

This issue was reported as a bug internally and has been fixed so far in Bamboo 4.2. Please upgrade Bamboo to overcome this issue

I'm on Bamboo 4.2.1 build 3213 - 28 Auth 12 and am still seeing this issue.

We're on Bamboo 4.2.0 build 3211 and we're still seeing this issue.

0 votes

Is it Windows?

I get the same problem. Running on Linux with Bamboo 4.1, Git 1.7. When I examine the git in the workarea, there is no remote defined to push to.

{code}

5:00pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $ git remote -v

5:00pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $ git status

# On branch BMGR-11

# Changes to be committed:

#

#modified: Scripts/src/main/scripts/BuilderMgr.sh

#modified: Scripts/src/main/scripts/DBUpdate.sh

#modified: Scripts/src/main/scripts/PreviewDBUpdate.sh

#modified: Scripts/src/main/scripts/PurgeRepository.sh

#modified: Scripts/src/main/scripts/SQLCheckIn.sh

#modified: Scripts/src/main/scripts/ServerChecker.sh

#modified: Scripts/src/main/scripts/UndoSQLCheckin.sh

#

# Untracked files:

# (use "git add <file>..." to include in what will be committed)

#

#build-number.txt

5:00pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $ git push

fatal: No configured push destination.

Either specify the URL from the command-line or configure a remote repository using

git remote add <name> <url>

and then push using the remote name

git push <name>

5:01pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $

{code}

I get the same problem. Running on Linux with Bamboo 4.1, Git 1.7. When I examine the git in the workarea, there is no remote defined to push to.

{code}

5:00pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $ git remote -v

5:00pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $ git status

# On branch BMGR-11

# Changes to be committed:

#

#modified: Scripts/src/main/scripts/BuilderMgr.sh

#modified: Scripts/src/main/scripts/DBUpdate.sh

#modified: Scripts/src/main/scripts/PreviewDBUpdate.sh

#modified: Scripts/src/main/scripts/PurgeRepository.sh

#modified: Scripts/src/main/scripts/SQLCheckIn.sh

#modified: Scripts/src/main/scripts/ServerChecker.sh

#modified: Scripts/src/main/scripts/UndoSQLCheckin.sh

#

# Untracked files:

# (use "git add <file>..." to include in what will be committed)

#

#build-number.txt

5:00pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $ git push

fatal: No configured push destination.

Either specify the URL from the command-line or configure a remote repository using

git remote add <name> <url>

and then push using the remote name

git push <name>

5:01pm releng@seq01 /prodinfolocal/BambooHome/xml-data/build-dir/VM-SG1-JOB1 $

{code}

0 votes

the changes are not pushed from that directory anyway, they use a separate directory on the server.

@Erik, your problem looks completely different from topic.

@rafi -- I got the same error message on the Bamboo Job Summary page as the original poster did, sorry I did not make that clear.

@Prezemek -- If the changes are not pushed from the Job's build directory, what directory are they pushed from? The user that Bamboo runs as has no problem pushing changes to the remote repository if the repository is cloned using "git clone".

0 votes

@Erik - server_home_dir/xml-data/build-dir/serverSide/planKey

@Prezemek -- finally got a chance to look in the server_home_dir/xml-data/build-dir/serverSide/planKey directory. But the serverSide directory is completely empty. Guess I will have to Report A Bug.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 10 hours ago in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

153 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you