Skip to content

[Refactor] Seperate CI config of ray-operator and apiserver e2e tests #3660

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
Open
2 tasks done
kenchung285 opened this issue May 22, 2025 · 0 comments · May be fixed by #3614
Open
2 tasks done

[Refactor] Seperate CI config of ray-operator and apiserver e2e tests #3660

kenchung285 opened this issue May 22, 2025 · 0 comments · May be fixed by #3614
Labels
enhancement New feature or request triage

Comments

@kenchung285
Copy link
Contributor

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

Current CI jobs of ray-operator e2e tests and apiserver e2e tests use the same YAML files, while kubectl-plugin use an independent YAML file. This makes e2e tests of apiserver less discoverable in .buildkite/test-e2e.yml.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@kenchung285 kenchung285 added enhancement New feature or request triage labels May 22, 2025
@kenchung285 kenchung285 linked a pull request May 22, 2025 that will close this issue
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Refactor] Seperate CI config of ray-operator and apiserver e2e tests kenchung285/kuberay
1 participant
@kenchung285