ci: add github actions workflow to run go envtest e2e tests#40
Open
jiridanek wants to merge 4 commits intokubewharf:mainfrom
Open
ci: add github actions workflow to run go envtest e2e tests#40jiridanek wants to merge 4 commits intokubewharf:mainfrom
jiridanek wants to merge 4 commits intokubewharf:mainfrom
Conversation
…est envtest and k8s for the test This is taken from kubebuilder 3.15
Author
|
Here's the test running on my fork, https://github.com/jiridanek/kubezoo/actions/runs/9224716083/job/25380566652 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
ci enhancement
What this PR does / why we need it:
Runs the remaining tests, followup to
Which issue(s) this PR fixes:
Special notes for your reviewer:
I had to update go, kubebuilder, and k8s to make this run. If updating go is not acceptable, please tell and I'll think of a different approach.
The issue that forces me to update go is described in my description of #39 .