ComputingGit < Main

Tags: view all tags

As everyone knows, it is particularly tricky to use GIT in our network. We need a proxy to talk to servers outside research networks. 

For GitHub clones, this will do:

<verbatim>
export https_proxy=http://newman.ultralight.org:3128
export http_proxy=http://newman.ultralight.org:3128
</verbatim>

But to commit back, I had to edit the file $REPO/.git/config and add my username to the following line :

<verbatim>
        url = https://samircury@github.com/samircury/CMSSW-benchmarks.git
</verbatim>

Which didn't have it before. Also, after git push origin master I got :

<verbatim>
-bash-4.1$ git push origin master
Password: 
Counting objects: 10, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (8/8), done.
error: RPC failed; result=22, HTTP code = 0
Writing objects: 100% (8/8), 3.53 MiB, done.
Total 8 (delta 1), reused 0 (delta 0)
</verbatim>

Then found [[http://stackoverflow.com/questions/11498337/git-push-all-is-failing-on-rpc-failed-result-22-http-code-0][here]]

That a workaround is to increase the HTTP buffer :

<verbatim>
git config http.postBuffer 524288000
</verbatim>

There is probably a better way to do both things, but these work for me now. Feel free to update with the better ways.

-- Main.samir - 2014-08-26

Topic revision: r1 - 2014-08-26 - samir

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback