Organize the sig-windows board

[jsturtevant]

As part of cleaning up the Windows tests we discussed in our sig meeting this week of creating a smaller dashboard that would be the "signal" for windows. We discussed keeping this dashboard smaller than the current https://testgrid.k8s.io/sig-windows-releases board and having criteria for how a test can be added to the new dash.

This is a proposal for adding only our release-informing (https://testgrid.k8s.io/sig-release-master-informing) jobs initially to a new sig-windows-signal dashboard so we can make these consistently green and then evaluate adding other tests (maybe presubmits or post submits?)

Going to hold for comment from for others who maintain tests: @jayunit100 @ravisantoshgudimetla @pjh @jeremyje @marosset @claudiubelu @chewong

/hold

fyi - I dropped our 1.17 tests as it is now longer actively maintained: https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md#non-active-branch-history

[jsturtevant]

Do we want to move the GCE configs into the config/jobs/kubernetes-sigs/sig-windows folder? I think this is the folder where sig jobs are prefered to live.

[jsturtevant]

@jeremyje @pjh Any thoughts on if these should be consolidated?

[jsturtevant]

I called it signal so we could add non informing jobs to it later if we wanted. Not tied to the name

[chewong]

/lgtm

[marosset]

/approve
/hold cancel

[marosset]

/assign @jeremyje @pjh

[marosset]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chewong, jsturtevant, marosset

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes-sigs/sig-windows/OWNERS [chewong,jsturtevant,marosset]
• config/jobs/kubernetes/sig-windows/OWNERS [chewong,jsturtevant,marosset]
• config/testgrids/kubernetes/sig-windows/OWNERS [chewong,marosset]

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]

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

• key release-1.17-windows.yaml using file ``
• key sig-windows-config.yaml using file config/jobs/kubernetes-sigs/sig-windows/sig-windows-config.yaml
• key windows-gce.yaml using file config/jobs/kubernetes/sig-windows/windows-gce.yaml

In response to this:

As part of cleaning up the Windows tests we discussed in our sig meeting this week of creating a smaller dashboard that would be the "signal" for windows. We discussed keeping this dashboard smaller than the current https://testgrid.k8s.io/sig-windows-releases board and having criteria for how a test can be added to the new dash.

This is a proposal for adding only our release-informing (https://testgrid.k8s.io/sig-release-master-informing) jobs initially to a new sig-windows-signal dashboard so we can make these consistently green and then evaluate adding other tests (maybe presubmits or post submits?)

Going to hold for comment from for others who maintain tests: @jayunit100 @ravisantoshgudimetla @pjh @jeremyje @marosset @claudiubelu @chewong

/hold

fyi - I dropped our 1.17 tests as it is now longer actively maintained: https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md#non-active-branch-history

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.