| commit | 7303ecf220ab1d616da726f99bf70116bd07eec6 | [log] [tgz] |
|---|---|---|
| author | dnj <dnj@chromium.org> | Wed May 31 20:52:44 2017 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed May 31 20:52:44 2017 |
| tree | d6eef8b3c59b4191bf15ed7fd566b65964f5dd17 | |
| parent | e6b32875ab0fafb2427a92412750a3071be3fc60 [diff] |
[vpython] Verify environment, named installs. Support installation of named enviornments, which are VirtualEnv whose name is explicitly specified instead of implicitly inferred from the supplied hash. This can be used by systems that want to use "vpython" to bootstrap a VirtualEnv in a known place instead of default usage. Since the specification is no longer always derived from the name, we add a step to verify that a given VirtualEnv actally matches the expected VirutalEnv. If it doesn't, it's considered incomplete and reprovisioned. This allows a path to upgrade named "vpython" roots from one installation to another, as well as additional cheap sanity checking to the basic "vpython" assumption that a stamped VirtualEnv is complete. BUG=None TEST=local - Ran "install" and setup normally, appears to work. R=sergeyberezin@chromium.org Review-Url: https://codereview.chromium.org/2918623003
go get -u github.com/luci/luci-go/client/cmd/... go get -u github.com/luci/luci-go/server/cmd/...
/common/... and /server/..../appengine/..., /client/... and /server/...; for example, the structures used by the server APIs. These are inherently APIs./appengine/....go1 contains the stable code.master constains the latest code.user.email and user.name are configured in git config.go get -u -t github.com/luci/luci-go/client/...go get -u github.com/maruel/pre-commit-go/cmd/... && pcgRun the following to setup the code review tool and create your first review:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" cd $GOROOT/github.com/luci/luci-go git checkout -b work origin/master # hack hack git commit -a -m "This is awesome\nR=joe@example.com" # This will ask for your Google Account credentials. git cl upload -s # Wait for LGTM over email. # Check the commit queue box in codereview website. # Wait for the change to be tested and landed automatically.
Use git cl help and git cl help <cmd> for more details.