project-infra,periodic: Add periodic to publish sig-failure reports from ci-health

[brianmcarey]

What this PR does / why we need it:

This requires kubevirt/ci-health#92

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

/cc @dhiller

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[dhiller]

Looks great, qq: why no sig-monitoring?

/hold to wait for the required PR to merge

[dhiller]

/approve

[brianmcarey]

Looks great, qq: why no sig-monitoring?

/hold to wait for the required PR to merge

I was just focusing on the larger SIGs for now but yes theres very little reason to not including sig monitoring here. I will add it now.

[dhiller]

/approve

Thank you @brianmcarey - since the ci-health PR is merged, we can take this in!

[brianmcarey]

/approve

Thank you @brianmcarey - since the ci-health PR is merged, we can take this in!

Thanks for the review @dhiller - I had to remove sig-monitoring as it is not supported by ci-health yet - https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/periodic-ci-health-sig-report-publish/1966401818988646400#1:build-log.txt%3A16

Tested the current version of the job config and its working - https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/logs/periodic-ci-health-sig-report-publish/1966404958110617600

/hold cancel

[dhiller]

/approve

🎉 @brianmcarey thanks!

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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:

• OWNERS [dhiller]

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

[kubevirt-bot]

@brianmcarey: Updated the job-config configmap in namespace kubevirt-prow at cluster default using the following files:

• key project-infra-periodics.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/project-infra/project-infra-periodics.yaml

Details

In response to this:

What this PR does / why we need it:

This requires kubevirt/ci-health#92

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

/cc @dhiller

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

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.