don't build or test vendor in test-infra

[BenTheElder]

/area bazel
/area jobs

[BenTheElder]

cc @ixdy

[spxtr]

Instead, just delete all _test.go files under vendor.

[BenTheElder]

@spxtr these are bazel tests so you'd have to fix up the BUILD files, I don't think there is any reason to run these. k/k already does this.

[spxtr]

Right, delete the test files and then rerun gazelle. When we switch to go dep it will do that for us, fortunately. Now we're in an awkward place where we have Godeps/Godeps.json but we don't actually use it as a source of truth.

[BenTheElder]

Right, delete the test files and then rerun gazelle. When we switch to go dep it will do that for us, fortunately. Now we're in an awkward place where we have Godeps/Godeps.json but we don't actually use it as a source of truth.

Sure we could (should?), but I don't see any reason to not also explicitly exclude them in the bazel jobs the same way that we do for k/k, which is somewhat orthogonal.

[krzyzacy]

I think we can have both. We should not need to build vendor stuff though.
Maybe a separate PR to delete all the _test.go files in test-infra?
/lgtm
/hold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, krzyzacy

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• prow/OWNERS [BenTheElder,krzyzacy]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[BenTheElder]

/hold cancel
see: #5301 for migrating to dep

[k8s-ci-robot]

@BenTheElder: I updated Prow config for you!

In response to this:

/area bazel
/area jobs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.