-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
RHIDP-5805 Optimize rhdh-e2e-runner Image Build Process #61263
RHIDP-5805 Optimize rhdh-e2e-runner Image Build Process #61263
Conversation
@gustavolira,
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
Hi @gustavolira. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-release-1.3.yaml
Outdated
Show resolved
Hide resolved
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-release-1.4.yaml
Outdated
Show resolved
Hide resolved
...istry/redhat-developer/rhdh/aks/helm/nightly/redhat-developer-rhdh-aks-helm-nightly-ref.yaml
Outdated
Show resolved
Hide resolved
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got two suggestions. Please see my inline comments.
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-main.yaml
Outdated
Show resolved
Hide resolved
ci-operator/step-registry/redhat-developer/rhdh/redhat-developer-rhdh-commands.sh
Outdated
Show resolved
Hide resolved
...tep-registry/redhat-developer/rhdh/release-1.3/redhat-developer-rhdh-release-1.3-commands.sh
Outdated
Show resolved
Hide resolved
...tep-registry/redhat-developer/rhdh/release-1.4/redhat-developer-rhdh-release-1.4-commands.sh
Outdated
Show resolved
Hide resolved
ci-operator/step-registry/redhat-developer/rhdh/redhat-developer-rhdh-commands.sh
Outdated
Show resolved
Hide resolved
5f68f1c
to
8b530b1
Compare
@gustavolira,
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
...erator/step-registry/redhat-developer/rhdh/nightly/redhat-developer-rhdh-nightly-commands.sh
Outdated
Show resolved
Hide resolved
ci-operator/step-registry/redhat-developer/rhdh/nightly/redhat-developer-rhdh-nightly-ref.yaml
Outdated
Show resolved
Hide resolved
ci-operator/step-registry/redhat-developer/rhdh/post-merge-push.sh
Outdated
Show resolved
Hide resolved
@gustavolira,
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
03db190
to
130ae8d
Compare
@gustavolira,
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-main.yaml
Show resolved
Hide resolved
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-main.yaml
Outdated
Show resolved
Hide resolved
@gustavolira just to simplify things, why don't only update images for main and after code freeze we will have similar config for 1.5 as well. anyway there isn't much work going on 1.3 and 1.4 so additional 15 min should not be a concern there. WDYT? although its just updating the image tag but my concern was if something goes wrong then not to break all the jobs. |
@gustavolira,
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/lgtm |
/pj-rehearse pull-ci-redhat-developer-rhdh-main-e2e-tests pull-ci-redhat-developer-rhdh-release-1.5-e2e-tests |
@subhashkhileri: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse ack |
@subhashkhileri: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
[REHEARSALNOTIFIER]
A total of 34 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse auto-ack |
@hector-vido: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gustavolira, hector-vido, subhashkhileri 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 |
/pj-rehearse pull-ci-redhat-developer-rhdh-release-1.5-e2e-tests-operator-nightly |
@hector-vido: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse ack |
@hector-vido: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@gustavolira: 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-sigs/prow repository. I understand the commands that are listed here. |
This PR updates the E2E testing process to always use the mirrored image from OpenShift CI instead of dynamically building the image during test runs.
Key Changes:
Remove Dynamic Image Builds: The pipeline will no longer build and push a temporary image for each PR.
Use OpenShift CI Mirror: All E2E tests will now use the pre-built image stored in the OpenShift CI registry (registry.ci.openshift.org/ci/rhdh-e2e-runner:).
Remove Image Promotion Step: Since we are no longer dynamically building the image, we no longer need to promote an image after a successful test run.
Manual Image Updates: Any updates to .ibm/images/ should be tested separately, manually pushed to Quay.io, and then the OpenShift CI mirror should be updated accordingly.