This is an old revision of the document!
This is a work-in-progress guide intended to help those that need to use Windows as their developer environment. It will address whatever issues developers commonly face, with hints/tools that have been tested and are in use by other OPNFV developers.
Source: Bryan Sullivan, AT&T
There are multiple ways to get git/gerrit working on Windows. Here are two:
This procedure may be terse, but will be clarified as needed and will be re-tested to make sure nothing is missing (steps that I took to get this working may have been forgotten in fumbling toward a solution…).
#!/bin/bash PATH=$PATH:"/C/Program Files/Git/bin" eval `ssh-agent` # add my private key ssh-add (path to your private key, e.g. /c/files/my-key) # (optional) go to your git clone home dir cd (path to where you clone repos, e.g. /c/files/git)
source ~/.bashrc
[filter "lfs"] clean = git-lfs clean %f smudge = git-lfs smudge %f required = true [user] name = (your ID on the gerrit server) email = *(your email)
git config --global http.proxy =(your proxy, e.g. http://proxy.example.com:8080)
[http] # proxy = http://proxy.example.com:8080
Host opnfv.org Hostname opnfv.org User (your ID known to the git server) IdentityFile (path to your private key, e.g. e.g. /c/files/my-key)
git clone https://gerrit.opnfv.org/gerrit/copper && scp -p -P 29418 blsaws@gerrit.opnfv.org:hooks/commit-msg copper/.git/hooks/