we are getting this error frequently:
build 24-Feb-2014 21:39:21 [exec] [RuntimeException] build 24-Feb-2014 21:39:21 [exec] Failed to execute git clone 'http://stash.mydomain.com/scm/myproject/myrepo.git' '/mydir/myrepo' && cd '/mydir/myrepo' && git remote add composer 'http://stash.mydomain.com/scm/myproject/myrepo.git' && git fetch composer build 24-Feb-2014 21:39:21 [exec] build 24-Feb-2014 21:39:21 [exec] error: The requested URL returned error: 400 while accessing http://stash.mydomain.com/scm/myproject/myrepo.git/info/refs build 24-Feb-2014 21:39:21 [exec] fatal: HTTP request failed
at other times it works.
in atlassian-stash.log we see this relevant line:
" It looks like we've received a 'dumb' protocol git request. "
but in atlassian-stash-access.log, the only git version is "git/1.7.10"
this is stash version 2.10.1.
any idea how to deal with this?
That doesn't sound right. My initial suspicion is that you have a proxy that is doing the wrong thing (but that's purely a guess). In any case would you mind raising a support ticket and attach your Stash logs?
To save a round-trip it might also help to capture the trace of the fetch using the following:
(You may need to modify the 'clone' part)
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot