Introduce ginkgo labels

sbueringer commented 2 months ago

Similar to Cluster API we should start using Ginkgo labels (https://github.com/kubernetes-sigs/cluster-api/issues/9620).

This should make it easier to label our tests correctly.

E.g. with the manual "tagging" + corresponding job config we have today we are always forced to implement govmomi tests when we want to add something for e.g supervisor.

(extracted from https://github.com/kubernetes-sigs/cluster-api/issues/9620)

sbueringer commented 2 months ago

/help

k8s-ci-robot commented 2 months ago

@sbueringer: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/3181): >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

kubernetes-sigs / cluster-api-provider-vsphere

Introduce ginkgo labels #3181

Guidelines