chore:(common-instancetypes): Add periodic and specify golang version

[0xFelix]

What this PR does / why we need it:

Add periodic to bump common-instancetype releases of release-1.2 branch
in Kubevirt's release-1.4 branch.

Specify that golang 1.22.9 should be installed in the presubmits of
common-instancetypes.

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:

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:

None

[0xFelix]

/rehearse all

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-8
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-validation-os
rehearsal-pull-common-instancetypes-kubevirt-functest
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-tumbleweed
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-7
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-9
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[0xFelix]

/rehearse all

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-7
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-9
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap
rehearsal-pull-common-instancetypes-kubevirt-functest-validation-os
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-8
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-tumbleweed
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[0xFelix]

/rehearse all

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-leap
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-8
rehearsal-pull-common-instancetypes-kubevirt-functest
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-9
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-stream-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora
rehearsal-pull-common-instancetypes-kubevirt-functest-fedora-arm64
rehearsal-pull-common-instancetypes-kubevirt-functest-opensuse-tumbleweed
rehearsal-pull-common-instancetypes-kubevirt-functest-validation-os
rehearsal-pull-common-instancetypes-kubevirt-functest-centos-7
rehearsal-pull-common-instancetypes-kubevirt-functest-ubuntu

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[0xFelix]

/retest

[jcanocan]

/lgtm

[0xFelix]

/rehearse rehearsal-pull-common-instancetypes-kubevirt-functest-fedora

[kubevirt-bot]

Rehearsal jobs created for this PR:

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[0xFelix]

/rehearse pull-common-instancetypes-kubevirt-functest-fedora

[kubevirt-bot]

Rehearsal jobs created for this PR:

rehearsal-pull-common-instancetypes-kubevirt-functest-fedora

You can trigger rehearsal for all jobs by commenting either /rehearse or /rehearse all
on this PR.

For a specific PR you can comment /rehearse {job-name}.

For a list of jobs that you can rehearse you can comment /rehearse ?.

[lyarwood]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lyarwood

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:

• github/ci/prow-deploy/files/jobs/kubevirt/common-instancetypes/OWNERS [lyarwood]

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

[kubevirt-bot]

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

• key common-instancetypes-periodics.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/common-instancetypes/common-instancetypes-periodics.yaml
• key common-instancetypes-presubmits.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/common-instancetypes/common-instancetypes-presubmits.yaml

In response to this:

What this PR does / why we need it:

Add periodic to bump common-instancetype releases of release-1.2 branch
in Kubevirt's release-1.4 branch.

Specify that golang 1.22.9 should be installed in the presubmits of
common-instancetypes.

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:

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:

None

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.