feat: add built-in run_test_experiment job to test the mlflow server internally so its super easy to test if it actually works e2e

This commit is contained in:
Tomasz Dłuski
2023-11-05 21:15:28 +01:00
parent 1e92560fb5
commit e9030c867d
4 changed files with 49 additions and 9 deletions

View File

@@ -67,6 +67,25 @@ services:
command: tcp db:3306 -t 90s -i 250ms
networks:
- internal
run_test_experiment:
build:
context: ./test_experiment
dockerfile: Dockerfile
depends_on:
- "mlflow"
environment:
- AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID}
- AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY}
- AWS_DEFAULT_REGION=${AWS_REGION}
- MLFLOW_S3_ENDPOINT_URL=http://s3:9000
- MLFLOW_TRACKING_URI=http://mlflow:5000
entrypoint: >
/bin/sh -c "
python3 mlflow_tracking.py;
exit 0;
"
networks:
- internal
networks:
internal:
public: