Find Questions…

Close ×
First time here? Check out the FAQ!

Bamboo git integration using Gatekeeper merge fails

ecopony asked this question · 21 karma ·

We are trying to set up git integration using the Gatekeeper automatic merging configuration. Our build is able to checkout latest from the branch and run the build, but when the build is successful, the push back to master fails.

From what we see in the logs, it is trying to push using a port and username that is different from our git configuration: ssh://56c2ece4-23a9-41c0-b98c-08a2817ce780@127.0.0.1:43221/hummingbird.git

We don't know where this username (56c2ece4-23a9-41c0-b98c-08a2817ce780) and port (43221) is coming from to form this connection string. Why is it not trying to push to master on the repository URL that we have configured (ssh://git@servername/hummingbird.git)?

Full log follows:

2012-05-15 11:42:26,239 WARN [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-9] [ChainExecutionManagerImpl] Exception during push: command [/usr/local/bin/git, push, ssh://56c2ece4-23a9-41c0-b98c-08a2817ce780@127.0.0.1:43221/hummingbird.git, master] failed with code 128. Working directory was [/sdb3/usr/local/atlassian/bamboo/Bamboo-4.0.1-home/xml-data/build-dir/serverSide/JCONT-HBIRD1-7/mergeWorkspace]. stderr: fatal: The remote end hung up unexpectedlyfatal: The remote end hung up unexpectedly stdout: fatal: The remote end hung up unexpectedlyfatal: The remote end hung up unexpectedly

2012-05-15 11:42:26,239 WARN [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-9] [ChainExecutionManagerImpl] Unable to push JCONT-HBIRD1-7 merge result: MergeResultSummaryImpl{integrationStrategy='GATE_KEEPER', mergeState='SUCCESS', pushState='FAILED', failureReason='Push command error: fatal: The remote end hung up unexpectedlyfatal: The remote end hung up unexpectedly', integrationBranchVcsKey='1f9ebcd5f8ce4b57800671e07020dcde5febb191', mergeResultVcsKey='null', integrationRepositoryId=8421400, integrationRepositoryBranchName='master', branchTargetVcsKey='ee5624de83560e86dcdfc0f8d62b29537dfd889b', branchName='bugfix-branch'}

2012-05-15 11:42:26,695 INFO [qtp764590486-10] [AccessLogFilter] ringhe GET http://developerland.jamasoftware.net:8086/rest/api/latest/result/status/JCONT-HBIRD1-7?expand=stages.stage.results.result&_=1337107346655 88163kb

2012-05-15 11:42:26,717 INFO [qtp764590486-11] [AccessLogFilter] ringhe GET http://developerland.jamasoftware.net:8086/chain/result/viewChainResult.action?planKey=JCONT-HBIRD1&buildNumber=7 86705kb

2012-05-15 11:42:27,071 ERROR [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-9] [ChainExecutionManagerImpl] Failed to push for plan-result: JCONT-HBIRD1-7. Push command error: fatal: The remote end hung up unexpectedlyfatal: The remote end hung up unexpectedly

686 views

Rafael Bodill · 26 karma ·

Can you share the solution ?

One Answer:

Przemek Bruski [Atlassian] · 13,378 karma ·

We don't know where this username (56c2ece4-23a9-41c0-b98c-08a2817ce780) and port (43221) is coming from to form this connection string. Why is it not trying to push to master on the repository URL that we have configured (ssh://git@servername/hummingbird.git)?

The address is Bamboo's internal proxy, that's normal.

You should contact support about the 'push' problem.

ecopony · 21 karma ·

Will do. Thanks for the help!

Looking for something else?

Find Questions…

or Browse other questions tagged:

or Ask a Question