[ci/release] Trigger Ray release by running a Bazel binary#52962
[ci/release] Trigger Ray release by running a Bazel binary#52962
Conversation
|
@aslonnie Instead of creating a custom cluster env and inject its ID, I think I can also intercept the part where it creates the cluster env in However, |
| try: | ||
| cluster_manager.cluster_env_id = cluster_env_id | ||
| cluster_manager.build_cluster_env() | ||
| cluster_manager.fetch_build_info() |
There was a problem hiding this comment.
this function doesn't even exist anymore
| return f"test_env_{image_normalized}_{test_name}" | ||
|
|
||
|
|
||
| def create_cluster_env_from_image( |
There was a problem hiding this comment.
yeah, I had a look. this is too similar to the one in minimal.py. these two should be merged.
There was a problem hiding this comment.
oh I didn't realize the commits were not pushed yet... pushed now
aslonnie
left a comment
There was a problem hiding this comment.
the two functions are still not merged.
|
2 functions are merged and the one in |
|
Triggered a test from release pipeline to make sure the code in |
|
Release test is still passing: https://buildkite.com/ray-project/release/builds/45209#01975b3f-99ac-4b91-b368-088def773260 |
- Add a flag to specify release image used for release tests - If image is specified, create/reuse a custom cluster environment and use its ID to trigger release tests with - If cluster env ID is already specified, the pipeline would not create another cluster env but choose to reuse the custom one we created - Add data deps so this script can be run with Bazel - A lot of the code in `create_cluster_env_from_image` is reused from `minimal.py` --------- Signed-off-by: kevin <kevin@anyscale.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
- Add a flag to specify release image used for release tests - If image is specified, create/reuse a custom cluster environment and use its ID to trigger release tests with - If cluster env ID is already specified, the pipeline would not create another cluster env but choose to reuse the custom one we created - Add data deps so this script can be run with Bazel - A lot of the code in `create_cluster_env_from_image` is reused from `minimal.py` --------- Signed-off-by: kevin <kevin@anyscale.com> Co-authored-by: Lonnie Liu <95255098+aslonnie@users.noreply.github.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
create_cluster_env_from_imageis reused fromminimal.py