Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MULTIARCH-4642: Enabling HCP with IBMZ workflow in 4.16 periodic job runs #51493

Merged
merged 16 commits into from May 13, 2024
Merged

MULTIARCH-4642: Enabling HCP with IBMZ workflow in 4.16 periodic job runs #51493

merged 16 commits into from May 13, 2024

Conversation

veera-damisetti
Copy link
Contributor

Enabling HCP IBMZ workflow for 4.16 periodic jobs

Added :

New config and job in 4.16 periodics

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 30, 2024
@openshift-ci openshift-ci bot requested review from csrwng and enxebre April 30, 2024 04:00
@veera-damisetti
Copy link
Contributor Author

/label tide/merge-method-squash

@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Apr 30, 2024
@veera-damisetti
Copy link
Contributor Author

/retest required

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 2, 2024

@veera-damisetti: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test app-ci-config-dry
  • /test boskos-config
  • /test boskos-config-generation
  • /test build-clusters
  • /test build01-dry
  • /test build02-dry
  • /test build03-dry
  • /test build04-dry
  • /test build05-dry
  • /test build09-dry
  • /test build10-dry
  • /test check-gh-automation
  • /test check-gh-automation-tide
  • /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 hosted-mgmt-dry
  • /test jira-lifecycle-config
  • /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 stackrox-stackrox-stackrox-stackrox-check
  • /test step-registry-metadata
  • /test step-registry-shellcheck
  • /test sync-rover-groups
  • /test vsphere02-dry
  • /test yamllint

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-master-step-registry-metadata
  • pull-ci-openshift-release-master-step-registry-shellcheck
  • pull-ci-openshift-release-openshift-image-mirror-mappings
  • pull-ci-openshift-release-yamllint

In response to this:

/retest required

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.

@veera-damisetti
Copy link
Contributor Author

/test all

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@veera-damisetti: 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
periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance N/A periodic Periodic changed
periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-mce-ibmz-conformance N/A periodic Ci-operator config changed
periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-mce-ibmz-conformance N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 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 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 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.

@veera-damisetti
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-mce-ibmz-conformance

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 7, 2024

@veera-damisetti: all tests passed!

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.

@veera-damisetti veera-damisetti changed the title [WIP] Enabling HCP with IBMZ workflow in 4.16 periodic job runs Enabling HCP with IBMZ workflow in 4.16 periodic job runs May 8, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 8, 2024
@veera-damisetti
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@veera-damisetti: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 8, 2024
@veera-damisetti
Copy link
Contributor Author

/lgtm

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 8, 2024

@veera-damisetti: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

@veera-damisetti
Copy link
Contributor Author

/assign @phani2898

@veera-damisetti
Copy link
Contributor Author

/assign @csrwng

@phani2898
Copy link
Contributor

/lgtm

@phani2898
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 8, 2024
@veera-damisetti veera-damisetti changed the title Enabling HCP with IBMZ workflow in 4.16 periodic job runs MULTIARCH-3763 : Enabling HCP with IBMZ workflow in 4.16 periodic job runs May 8, 2024
@veera-damisetti veera-damisetti changed the title MULTIARCH-3763 : Enabling HCP with IBMZ workflow in 4.16 periodic job runs MULTIARCH-4642: Enabling HCP with IBMZ workflow in 4.16 periodic job runs May 8, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 8, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 8, 2024 •
edited by openshift-ci bot

@veera-damisetti: This pull request references MULTIARCH-4642 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

Enabling HCP IBMZ workflow for 4.16 periodic jobs

Added :

New config and job in 4.16 periodics

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 openshift-eng/jira-lifecycle-plugin repository.

@veera-damisetti
Copy link
Contributor Author

@csrwng Can you please review this PR

@LiangquanLi930
Copy link
Member

/lgtm

@jparrill
Copy link
Contributor

/approve

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill, LiangquanLi930, phani2898, veera-damisetti

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 32c23b5 into openshift:master May 13, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@csrwng csrwng Awaiting requested review from csrwng

@enxebre enxebre Awaiting requested review from enxebre

Assignees

@csrwng csrwng

@phani2898 phani2898

@LiangquanLi930 LiangquanLi930

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Milestone
No milestone
7 participants
@veera-damisetti @openshift-ci-robot @phani2898 @LiangquanLi930 @jparrill @csrwng @openshift-merge-robot