Skip to content

Add PR bundle image - #792

Open
Vincent056 wants to merge 1 commit into
masterfrom
new_bundle_trigger_pr
Open

Add PR bundle image#792
Vincent056 wants to merge 1 commit into
masterfrom
new_bundle_trigger_pr

Conversation

@Vincent056

Copy link
Copy Markdown
Contributor

This commit introduces a new task to the Tekton pipeline that waits for the operator image to become available. The task includes parameters for the operator image, maximum wait time, and check interval, along with a script to handle the waiting logic. The init task is updated to run after this new task, ensuring proper sequencing in the pipeline.

@Vincent056 Vincent056 changed the title Add PR bundle image DRAFT: Add PR bundle image Nov 20, 2025
@Vincent056
Vincent056 force-pushed the new_bundle_trigger_pr branch 2 times, most recently from 71b30cf to c742bc2 Compare November 20, 2025 13:02
@openshift-ci
openshift-ci Bot requested review from xiaojiey and yuumasato November 20, 2025 13:07
@openshift-ci

openshift-ci Bot commented Nov 20, 2025

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Vincent056

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Nov 20, 2025
@Vincent056
Vincent056 force-pushed the new_bundle_trigger_pr branch 4 times, most recently from e54255c to a472d52 Compare November 20, 2025 13:53
@yuumasato

Copy link
Copy Markdown
Contributor

This is very interesting @Vincent056
The EC tests didn't flag wait-for-operator-image as untrusted, I wonder if it will continue that way if merged.

name: CHAINS-GIT_COMMIT
value: $(tasks.clone-repository.results.commit)
tasks:
- name: wait-for-operator-image

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Vincent056 I'm starting to think that we need to have a separate pipeline that builds the Bundle image from the PR changes.

I say this because ideally we should be building the images only when relevant changes to each image is made:

  • We only build the operator image when changes for the operator code are made
  • We should only build the bundle image when relevant changes for the bundle are made.

There will be cases when we may only need or want to build the bundle image. In this case there is no operator image build to wait for.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think bundle should always be built as long as we have triggered operator build in a PR.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is why we need to have this changed in the operator image pipeliene.

The bundle pipeline may not always have an operator image to wait for if only the bundle image was triggered.
A bundle build should not require an operator build to happen as well.

@yuumasato

yuumasato commented Dec 12, 2025

Copy link
Copy Markdown
Contributor

@Vincent056 I have tried a different but similar approach in 89b3f9a

Edit: totally wrong link.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 12, 2025
This commit introduces a new task to the Tekton pipeline that waits for the operator image to become available. The task includes parameters for the operator image, maximum wait time, and check interval, along with a script to handle the waiting logic. The init task is updated to run after this new task, ensuring proper sequencing in the pipeline.
@Vincent056
Vincent056 force-pushed the new_bundle_trigger_pr branch from a472d52 to 2aa7a67 Compare December 12, 2025 15:45
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 12, 2025
@Vincent056 Vincent056 changed the title DRAFT: Add PR bundle image Add PR bundle image Dec 12, 2025
@openshift-ci

openshift-ci Bot commented Dec 12, 2025

Copy link
Copy Markdown
Contributor

@Vincent056: The following tests 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/prow/e2e-bundle-aws 2aa7a67 link false /test e2e-bundle-aws
ci/prow/e2e-bundle-aws-upgrade 2aa7a67 link false /test e2e-bundle-aws-upgrade

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot

Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 16, 2026
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 16, 2026
@openshift-merge-robot

Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

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.

@openshift-bot

Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants