Skip to content

Commit 6c2f03f

Browse files
authored
Deploy to ACI error fix (#126)
1 parent 8d1be26 commit 6c2f03f

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

code/scoring/conda_dependencies.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ dependencies:
2828
- azureml-model-management-sdk==1.0.1b6.post1
2929
- azureml-sdk==1.0.74
3030
- scipy==1.3.1
31-
- scikit-learn==0.21.3
31+
- scikit-learn==0.22
3232
- pandas==0.25.3
3333
- numpy==1.17.3
3434
- joblib==0.14.0

docs/getting_started.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,8 @@ specified).
182182

183183
* The second stage of the pipeline, **Train model**, triggers the run of the ML Training Pipeline. The training pipeline will train, evaluate, and register a new model. The actual computation is performed in an [Azure Machine Learning Compute cluster](https://docs.microsoft.com/en-us/azure/machine-learning/service/how-to-set-up-training-targets#amlcompute). In Azure DevOps, this stage runs an agentless job that waits for the completion of the Azure ML job, so it can wait for training completion for hours or even days without using agent resources.
184184

185+
**Note:** If the model evaluation determines that the new model does not perform better than the previous one then the new model will not be registered and the pipeline will be cancelled.
186+
185187
* The third stage of the pipeline, **Deploy to ACI**, deploys the model to the QA environment in [Azure Container Instances](https://azure.microsoft.com/en-us/services/container-instances/). It then runs a *smoke test* to validate the deployment, i.e. sends a sample query to the scoring web service and verifies that it returns a response in the expected format.
186188

187189
Wait until the pipeline finished and make sure there is a new model in the **ML Workspace**:

0 commit comments

Comments
 (0)