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

Update Submariner dependencies to v0.20.0-rc0 #3294

Merged
merged 1 commit into from
Feb 5, 2025
Merged

Update Submariner dependencies to v0.20.0-rc0 #3294

merged 1 commit into from
Feb 5, 2025

Conversation

submariner-bot
Copy link
Contributor

Update Submariner dependencies to v0.20.0-rc0

@submariner-bot
Copy link
Contributor Author

🤖 I see this PR is using the local branch workflow, ignoring it on my side, have fun!
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@submariner-bot submariner-bot added automated e2e-all-k8s Fake label to keep releases from tripping ready-to-test When a PR is ready for full E2E testing labels Feb 5, 2025
@submariner-bot submariner-bot enabled auto-merge (rebase) February 5, 2025 19:07
@submariner-bot submariner-bot mentioned this pull request Feb 5, 2025
Merged
@dfarrell07 dfarrell07 added ready-to-test When a PR is ready for full E2E testing and removed ready-to-test When a PR is ready for full E2E testing labels Feb 5, 2025
@dfarrell07
Copy link
Member

I think the GHA "label added" events for the K8s-all and ready-to-test were not both processed. Re-adding the label got the jobs started.

@dfarrell07 dfarrell07 added e2e-all-k8s Fake label to keep releases from tripping and removed e2e-all-k8s Fake label to keep releases from tripping labels Feb 5, 2025
@dfarrell07
Copy link
Member

Actually the e2e-default and the e2e-full GHAs seem to be working as expected. The jobs that are marked as expected are weird - for example I don't see how a "E2E (1.26)" job is configured for this branch.

Maybe it's something to do with the required status being off because it's a new release-0.20 branch.

@dfarrell07 dfarrell07 mentioned this pull request Feb 5, 2025
Merged
@submariner-bot submariner-bot merged commit d20fce2 into release-0.20 Feb 5, 2025
80 checks passed
@tpantelis
Copy link
Contributor

Actually the e2e-default and the e2e-full GHAs seem to be working as expected. The jobs that are marked as expected are weird - for example I don't see how a "E2E (1.26)" job is configured for this branch.

Maybe it's something to do with the required status being off because it's a new release-0.20 branch.

yeah I had setup release-0.20 the same as 19 for now. I updated it

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

@dfarrell07 dfarrell07 dfarrell07 approved these changes

@tpantelis tpantelis tpantelis approved these changes

@aswinsuryan aswinsuryan aswinsuryan approved these changes

@maayanf24 maayanf24 Awaiting requested review from maayanf24 maayanf24 is a code owner

@Oats87 Oats87 Awaiting requested review from Oats87 Oats87 is a code owner

@skitt skitt Awaiting requested review from skitt skitt is a code owner

@sridhargaddam sridhargaddam Awaiting requested review from sridhargaddam sridhargaddam is a code owner

@vthapar vthapar Awaiting requested review from vthapar vthapar is a code owner

@yboaron yboaron Awaiting requested review from yboaron yboaron is a code owner

Assignees
No one assigned
Labels
automated e2e-all-k8s Fake label to keep releases from tripping ready-to-test When a PR is ready for full E2E testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@submariner-bot @dfarrell07 @tpantelis @aswinsuryan