Run more automated checks on kube-deploy repo

[krousey]

We should run the following checks on PRs and in CI:

• go vet
• gofmt
• verify vendor depencies are correct (this is partially accomplished by build today, but it'd be nice to have better messaging around this)
• code doesn't need to be regenerated (deepcopy, conversion, clients, ...)
• BUILD files don't have to be regenerated

[vaibhavsingh97]

Hi @krousey Can I take this issue? Any resources to fix this issue will be a great help :)

[krousey]

@vaibhavsingh97 Sure! go vet and go fmt would be the easiest to start with, and they cover areas that aren't someone protected against by our current CI build and test.

I started a CI scripts directory here: https://github.com/kubernetes/kube-deploy/tree/master/scripts

Here are the PRs I submitted to turn on build and testing in CI and on PRs. Hopefully that will be instructive enough.

• Add a couple of scripts for CI #584
• Remove newline from test script #590
• Adding PR jobs for kube-deploy kubernetes/test-infra#6761
• Add testing image for kube-deploy with etcd installed kubernetes/test-infra#6787
• Turning on PR testing for kube-deploy kubernetes/test-infra#6792

Also, if you're running the scripts locally, I would recommend Go 1.9+ because they changed the way go tools handle the vendor directory to make it easier.

[rsdcastro]

This issue was moved to kubernetes-sigs/cluster-api#43