[Feature] Migrate CI infra from GitHub Actions to Buildkite

[kevin85421]

Search before asking

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

Description

KubeRay CI has some resource limitations (especially CPU), and thus most sample YAMLs cannot be tested in KubeRay CI (GitHub Actions). Hence, I open this issue to track the progress of configuration tests on Ray CI. See #678 for more details.

Use case

No response

Related issues

#678
#642
#731

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[DmitriGekhtman]

The more appropriate long-term move would be to unify KubeRay's CI infrastructure with the Ray CI's Buildkite infra. That way, we could run tests per-commit in the KubeRay CI.

[krfricke]

cc @zhe-thoughts @matthewdeng for visibility. I'm helping set up the KuberRay CI this week

[kevin85421]

Thanks @krfricke! This is the most important item for KubeRay v0.5.0.

[zhe-thoughts]

Thanks @kevin85421 , what is the ETA for KubeRay v0.5.0? (What is the default release cadence)?

[gvspraveen]

Currently we are targeting every alternate Ray release. So next one will be after Ray 2.4 (some time early April)