Arvados

1. Ensure $GOPATH points somewhere (maybe ~/go)
2. go get github.com/kardianos/govendor
3. Either
   • add a symlink to a checked-out arvados tree:
     mkdir -p ${GOPATH}/src/git.curoverse.com && ln -sfT ${WORKSPACE} ${GOPATH}/src/git.curoverse.com/arvados.git
   • ...or check out the arvados tree the normal Go way:
     go get git.curoverse.com/arvados.git
4. cd ${GOPATH}/src/git.curoverse.com/arvados.git && ${GOPATH}/bin/govendor update +v

"+v" means all vendor packages. You can also update a single dependency, etc. See https://github.com/kardianos/govendor

Now $GOPATH/src/git.coroverse.com/arvados.git/vendor/vendor.json is updated with new version specs. Run tests, commit, push.

11720-govendor @ b1b7a0be3c789795675e731c8c64bee3cb6d718c

example run https://ci.curoverse.com/job/developer-run-tests-remainder/297/console

11720-govendor @ 865d1b22bb42a6c89ca9aa9a3513f3c61c6547c7 (missed adding vendor/.gitignore because it said to ignore itself)

in build/run-tests.sh

cd "$GOPATH/src/git.curoverse.com/arvados.git" && \
    "$GOPATH/bin/govendor" sync -v || \
        fatal "govendor sync failed" 

shouldn't be using GOROOT ? I had the impression GOPATH is a colon/comma separated values of the path, that in 95% of the time is only onve value,

but I could be wrong and this changed in later versions of Go

Nico César wrote:

shouldn't be using GOROOT ? I had the impression GOPATH is a colon/comma separated values of the path, that in 95% of the time is only onve value,

That's true in general, but in run-tests.sh we set GOPATH to {tempdir}/GOPATH so I don't think we need to support the multi-value case.

(GOROOT is where stdlib and the go tools themselves live)

besides that LGTM