ray/release/requirements.txt

# ray
https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl
click
anyscale>0.5.0
slackclient
boto3
jinja2
PyGithub
pydantic
pyyaml
typer[all]
toml
python-dotenv
expiringdict
requests
pytz
git+https://github.com/ray-project/xgboost_ray.git#egg=xgboost_ray
git+https://github.com/ray-project/lightgbm_ray.git#lightgbm_ray
[ci/release] use s3 sync (#21626) Previous changes failed because a) permission errors b) unzip being unavailable at remote nodes. Instead we are using tar gzip archives now. This reverts commit 42bcab27e83d135fce2ca40f06f47465daedd09e. 2022-01-15 17:53:19 -08:00			`# ray`
			`https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-2.0.0.dev0-cp37-cp37m-manylinux2014_x86_64.whl`
[release] move release testing end to end script to main ray repo (#17070) 2021-07-14 21:39:07 +02:00			`click`
[ci/release] Update to recent anyscale API changes (#21149) Recent changes in the anyscale API rendered the current e2e script incompatible. This PR resolves these subtle API changes. 2022-01-04 11:21:47 +00:00			`anyscale>0.5.0`
[release] move release testing end to end script to main ray repo (#17070) 2021-07-14 21:39:07 +02:00			`slackclient`
			`boto3`
[ci/release] Refactor release test e2e into package (#22351) Adds a unit-tested and restructured ray_release package for running release tests. Relevant changes in behavior: Per default, Buildkite will wait for the wheels of the current commit to be available. Alternatively, users can a) specify a different commit hash, b) a wheels URL (which we will also wait for to be available) or c) specify a branch (or user/branch combination), in which case the latest available wheels will be used (e.g. if master is passed, behavior matches old default behavior). The main subpackages are: Cluster manager: Creates cluster envs/computes, starts cluster, terminates cluster Command runner: Runs commands, e.g. as client command or sdk command File manager: Uploads/downloads files to/from session Reporter: Reports results (e.g. to database) Much of the code base is unit tested, but there are probably some pieces missing. Example build (waited for wheels to be built): https://buildkite.com/ray-project/kf-dev/builds/51#_ Wheel build: https://buildkite.com/ray-project/ray-builders-branch/builds/6023 2022-02-16 17:35:02 +00:00			`jinja2`
[release] move release testing end to end script to main ray repo (#17070) 2021-07-14 21:39:07 +02:00			`PyGithub`
			`pydantic`
			`pyyaml`
			`typer[all]`
			`toml`
			`python-dotenv`
			`expiringdict`
			`requests`
			`pytz`
[CI/docs] Remove [default] from xgboost-ray (#19186) Co-authored-by: Kai Fricke <kai@anyscale.com> 2021-10-14 17:29:55 +02:00			`git+https://github.com/ray-project/xgboost_ray.git#egg=xgboost_ray`
[docs] Add LightGBM-Ray docs, update XGBoost-Ray docs (#17188) 2021-07-20 17:06:47 +02:00			`git+https://github.com/ray-project/lightgbm_ray.git#lightgbm_ray`