Intersmash - adding a periodic job configuration

[fabiobrz]

Intersmash - adding a periodic job configuration for running tests with prod deliverables

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@fabiobrz: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-Intersmash-intersmash-main-intersmash-e2e	Intersmash/intersmash	presubmit	Ci-operator config changed
periodic-ci-Intersmash-intersmash-main-periodic-intersmash-e2e-periodic	N/A	periodic	Periodic changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@fabiobrz: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test app-ci-config-dry
• /test boskos-config
• /test boskos-config-generation
• /test build01-dry
• /test build02-dry
• /test build03-dry
• /test build04-dry
• /test build05-dry
• /test build08-dry
• /test check-gh-automation
• /test ci-operator-config
• /test ci-operator-config-metadata
• /test ci-operator-registry
• /test ci-secret-bootstrap-config-validation
• /test ci-testgrid-allow-list
• /test clusterimageset-validate
• /test config
• /test core-valid
• /test deprecate-templates
• /test generated-config
• /test generated-dashboards
• /test hive-dry
• /test jira-lifecycle-config
• /test multi01-dry
• /test openshift-image-mirror-mappings
• /test ordered-prow-config
• /test owners
• /test pr-reminder-config
• /test prow-config
• /test prow-config-filenames
• /test prow-config-semantics
• /test pylint
• /test release-config
• /test release-controller-config
• /test secret-generator-config-valid
• /test services-valid
• /test step-registry-metadata
• /test step-registry-shellcheck
• /test supplemental-ci-images-mapping-files
• /test sync-rover-groups
• /test vsphere02-dry
• /test yamllint

The following commands are available to trigger optional jobs:

• /test arm01-dry
• /test build-clusters
• /test vsphere-dry

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-release-check-gh-automation
• pull-ci-openshift-release-master-build-clusters
• pull-ci-openshift-release-master-ci-operator-config
• pull-ci-openshift-release-master-ci-operator-config-metadata
• pull-ci-openshift-release-master-ci-operator-registry
• pull-ci-openshift-release-master-config
• pull-ci-openshift-release-master-core-valid
• pull-ci-openshift-release-master-deprecate-templates
• pull-ci-openshift-release-master-generated-config
• pull-ci-openshift-release-master-ordered-prow-config
• pull-ci-openshift-release-master-owners
• pull-ci-openshift-release-master-prow-config-filenames
• pull-ci-openshift-release-master-prow-config-semantics
• pull-ci-openshift-release-master-release-controller-config
• pull-ci-openshift-release-openshift-image-mirror-mappings
• pull-ci-openshift-release-yamllint

In response to this:

/test periodic-ci-Intersmash-intersmash-main-periodic-intersmash-e2e-periodic

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.

[fabiobrz]

/pj-rehearse

[fabiobrz]

/pj-rehearse

[fabiobrz]

/pj-rehearse ack

[tommaso-borgato]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabiobrz, tommaso-borgato

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:

• ci-operator/config/Intersmash/intersmash/OWNERS [fabiobrz,tommaso-borgato]
• ci-operator/jobs/Intersmash/intersmash/OWNERS [fabiobrz,tommaso-borgato]

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

[fabiobrz]

Thanks @tommaso-borgato, the rehearsal job is ok, we just need to tweak one failure on the Intersmash side (Kafka protocol for operator based provisioning) in case of productized deliverables.

[openshift-ci]

@fabiobrz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/rehearse/periodic-ci-Intersmash-intersmash-main-periodic-intersmash-e2e-periodic	fdd0004	link	unknown	/pj-rehearse periodic-ci-Intersmash-intersmash-main-periodic-intersmash-e2e-periodic

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.