sig,report: Include release branch failures in report

[brianmcarey]

What this PR does / why we need it:

With the release branch failures omitted from the report - the numbers displayed in the ci-health README do not match the number of failures in the report which can be confusing.

Include release branch job failures in the sig reports

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]

one question inline

[dhiller]

this might also pull in other jobs from the main branch. do we want that?

also do we not want to restrict from which release branches we want to pull in the results?

(maybe I am also overthinking here...)

Suggested change

	"compute": "sig-compute|sig-compute-serial|sig-compute-migrations|sig-operator|vgpu|sev",
	"compute": "(sig-compute|sig-compute-serial|sig-compute-migrations|sig-operator|vgpu|sev)(-1.[0-9]+)?",

[brianmcarey]

I am not sure @dhiller - I think if the e2e job name includes say sig-compute then we should be happy enough that sig-compute own the job. Also the metric includes any jobs with sig-compute in the name

ci-health/pkg/sigretests/main.go

Line 226 in 1d7b85c

case strings.Contains(job.jobName, "sig-compute") || strings.Contains(job.jobName, "vgpu"):

In a followup PR, I am going to split out sig-operator and add sig-monitoring to generate reports for each of those so that each badge will have its own linked report.

[brianmcarey]

What do you think @dhiller ?

[dhiller]

/approve