Some operations are sensitive to the version of Go that is used. In
the past, formatting of source differed depending on the
version. Right now it is the content of the vendor directory which
changes when switch back and forth between 1.12 and 1.13.

We don't want to impose a certain workflow on developers, like forcing
all invocations of Go to run inside a container. If developers want
that, they can set up their development environment accordingly.

But we should warn about this aspect to raise awareness. "make"
invocations which involve Go now compare against the projects Go
version (specified in travis.yml) once at the beginning. This is only
a warning because we don't know which future version will be
compatible with the project.

Vendor directory handling gets updated, too: verification is now a
separate script (became too complex for make) and there is a
corresponding "update-vendor.sh". In contrast to verification,
updating vendor is not integrated into make and thus itself invokes
the go version check.

This is the latest release. Updating is useful to ensure that we have
all of the latest fixes and enhancements.

Add new variables for 1.16 and remove 1.13

Do full git clones in travis

errors when the depth is exactly 50.

update Go mod support

Build Windows only for amd64

Signed-off-by: Deep Debroy <ddebroy@docker.com>

This script handles the necessary "replace" statements and determines
which packages need to be updated in lockstep.

It turned out that changes like
https://github.com/kubernetes-csi/csi-lib-utils/pull/33 should better
have been committed after `go mod tidy` because that adds some
indirect dependencies in that example.

The revised `test-vendor` checks for that and (just in case that this
ever becomes desired) allows projects to not have a vendor directory
when using `go mod`.

How to use `go mod` properly gets documented in the README.md, because
there are such pitfalls.

Enable hostpath expansion

build windows binaries with .exe suffix

Create 2-node kind cluster since topology support is added to hostpath

Signed-off-by: Mucahit Kurt <mucahitkurt@gmail.com>

prow.sh: install dep if needed

"make test-vendor" depends on dep if the current project uses
dep. Without it, the vendor directory checking was skipped under Prow.

Add rule for building Windows binaries

Signed-off-by: Deep Debroy <ddebroy@docker.com>

Update kind to v0.5.0

Fix CI jobs on Kubernetes master

changes to kind. There are 3 changes made to prow.sh:

1. Use a master commit of kind that includes the fix for Kubernetes
master.
2. Use git clone instead of git checkout (shallow) to source Kubernetes.
This lets kind correctly figure out the Kubernetes release tag.
3. Build kind with make install. The kind fix was not working correctly
when built with go build.

prow.sh: tag master images with a large version number

Add 1.15 jobs

with specific patch versions that kind 0.4.0 supports. Also, feature
gate setting is only supported on 1.15+ due to
kind.sigs.k8s.io/v1alpha3 and kubeadm.k8s.io/v1beta2 dependencies.

more flexible test driver config

By moving the code into a separate function, other CSI drivers have a
chance to overwrite it. For the hostpath driver itself we need the
ability to set the driver name depending on which revision is getting
installed.

build.make: allow repos to use 'go mod' for vendoring

How a repo does vendoring is detected based on the presence of
Gopkg.toml.

The vendor check with `dep` was all done locally, but the
corresponding check for `go mod` requires network access. The check
therefore gets skipped when running in the Prow CI in situations where
we are sure that it isn't needed (for example, in a periodic job).

update to Go 1.12.4

Kubernetes also requires 1.12. We pick the latest stable release
for CI builds.

prow.sh: skip sanity testing if component doesn't support it

Whether a component supports sanity testing depends on the
component. For example, csi-driver-host-path enables it because it
makes sense there (and only there). Letting the prow.sh script decide
whether it actually runs simplifies the job definitions in test-infra.