Skip to content
This repository was archived by the owner on Sep 9, 2026. It is now read-only.

OSAC-1675: Add E2E full-install presubmit workflow - #357

Merged
eliorerz merged 1 commit into
mainfrom
OSAC-1675-e2e-presubmit
Jun 26, 2026
Merged

eliorerz merged 1 commit into
mainfrom
OSAC-1675-e2e-presubmit

Conversation

@eliorerz

Copy link
Copy Markdown
Contributor

Summary

  • Adds e2e-vmaas-full-install.yml caller workflow that triggers on PRs to main
  • Calls osac-project/osac-test-infra/.github/workflows/e2e-vmaas-full-install.yml@main
  • Passes the PR's fork/branch as installer-repo and installer-ref so the E2E test deploys the actual PR content
  • Sets test-infra-repository to ensure osac-test-infra is checked out for tests/Containerfile

Test plan

  • Open a test PR and verify the E2E workflow triggers
  • Confirm the installer clone uses the PR branch (check "Install infrastructure operators" and "Install OSAC" step logs)
  • Verify workflow_dispatch works with default inputs

Trigger the e2e-vmaas-full-install reusable workflow from osac-test-infra
on PRs to main. The workflow clones osac-installer from the PR's
fork/branch (installer-repo + installer-ref) so the E2E tests exercise
the actual PR content, including submodules.
@openshift-ci-robot

openshift-ci-robot commented Jun 26, 2026

Copy link
Copy Markdown

@eliorerz: This pull request references OSAC-1675 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 "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Adds e2e-vmaas-full-install.yml caller workflow that triggers on PRs to main
  • Calls osac-project/osac-test-infra/.github/workflows/e2e-vmaas-full-install.yml@main
  • Passes the PR's fork/branch as installer-repo and installer-ref so the E2E test deploys the actual PR content
  • Sets test-infra-repository to ensure osac-test-infra is checked out for tests/Containerfile

Test plan

  • Open a test PR and verify the E2E workflow triggers
  • Confirm the installer clone uses the PR branch (check "Install infrastructure operators" and "Install OSAC" step logs)
  • Verify workflow_dispatch works with default inputs

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.

@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eliorerz

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

@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@eliorerz, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 50 minutes and 33 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 1b47ea57-bdd6-455a-a115-06a2144bb152

📥 Commits

Reviewing files that changed from the base of the PR and between bd3a98f and 1eff386.

📒 Files selected for processing (1)
  • .github/workflows/e2e-vmaas-full-install.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch OSAC-1675-e2e-presubmit

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@eliorerz eliorerz closed this Jun 26, 2026
@eliorerz eliorerz reopened this Jun 26, 2026
@eliorerz
eliorerz merged commit b6fa680 into main Jun 26, 2026
12 of 16 checks passed
@eliorerz
eliorerz deleted the OSAC-1675-e2e-presubmit branch June 26, 2026 16:41
@github-actions

Copy link
Copy Markdown

Re-triggered failed runs:

  • E2E VMaaS Full Install (#28246028221)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants