cloud-provider-gcp: run cloud-provider-gcp-tests by calling script

[justinsb]

We have a script that defines the desired content of this job,
in dev/ci/presubmits/cloud-provider-gcp-tests.

In general, we want to keep the logic in our own repo,
and keep (only) prow configuration in prow.

[justinsb]

This is in support of kubernetes/cloud-provider-gcp#916 , but is also working towards keeping non-prow logic out of prow config.

/assign @cheftako

[justinsb]

Bizarrely though, it looks like the tests are failing at head right now...

[hdp617]

This change makes sense to me.

@cheftako @YifeiZhuang Could you approve this change? Thanks!

[YifeiZhuang]

/LGTM
I am not an approver in the OWNER file.
cc. @aojea

[aojea]

/lgtm
/approve

cc:@xiaoweim

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, justinsb

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/cloud-provider-gcp/OWNERS [aojea]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@justinsb: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key cloud-provider-gcp-presubmits.yaml using file config/jobs/kubernetes/cloud-provider-gcp/cloud-provider-gcp-presubmits.yaml

Details

In response to this:

We have a script that defines the desired content of this job,
in dev/ci/presubmits/cloud-provider-gcp-tests.

In general, we want to keep the logic in our own repo,
and keep (only) prow configuration in prow.

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-sigs/prow repository.