Skip to content
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Merged
Changes from 1 commit
Commits
Show all changes
41 commits
Select commit Hold shift + click to select a range
0abdb5d
getting started
Aug 12, 2019
a460ab0
removed garbage
Aug 12, 2019
033dbbf
getting started update
Aug 13, 2019
2afe237
update IaC pipelines
Aug 13, 2019
5a1e994
document update progress
Aug 13, 2019
3459d7f
document update progress
Aug 13, 2019
67fd322
update document progress
Aug 13, 2019
d75895c
adjust image size
Aug 13, 2019
03b94ca
document update progress
Aug 13, 2019
9c43038
azure-cli to requirements
Aug 13, 2019
5f300f4
document update progress
Aug 13, 2019
e9fb924
document update progress
Aug 13, 2019
4eca7b1
document update progress
Aug 14, 2019
3c129b8
Update getting_started.md
eedorenko Aug 14, 2019
5c7ebe4
Update getting_started.md
eedorenko Aug 14, 2019
8fc0ba1
Update getting_started.md
eedorenko Aug 14, 2019
5a05f00
Update getting_started.md
eedorenko Aug 14, 2019
8b5b76a
Update getting_started.md
eedorenko Aug 14, 2019
a50b0d4
Update getting_started.md
eedorenko Aug 14, 2019
bd2a43b
Update getting_started.md
eedorenko Aug 14, 2019
f930580
Update getting_started.md
eedorenko Aug 14, 2019
e433ca8
Update getting_started.md
eedorenko Aug 14, 2019
a4f44bb
Update getting_started.md
eedorenko Aug 14, 2019
d4b343e
readme update
Aug 14, 2019
62377c5
Merge branch 'eedorenko/documentation-update' of https://github.com/m…
Aug 14, 2019
d421847
Update README.md
eedorenko Aug 14, 2019
5897a31
readme update
Aug 14, 2019
569b4ed
Merge branch 'eedorenko/documentation-update' of https://github.com/m…
Aug 14, 2019
3f6f056
update document progress
Aug 14, 2019
2b122c5
update documentation progress
Aug 15, 2019
4d34ace
azure-cli library update
Aug 15, 2019
71208d6
docker image update
Aug 15, 2019
9736e0a
docker image update
Aug 15, 2019
7b7e382
liniting
Aug 15, 2019
5294441
Update getting_started.md
eedorenko Aug 16, 2019
73db451
image update
Aug 16, 2019
0c3688d
Merge branch 'eedorenko/documentation-update' of https://github.com/m…
Aug 16, 2019
c8c2824
minor add and typo fix
Aug 16, 2019
48718f3
duplicate file paths and `code` snippet for file paths
eedorenko Aug 16, 2019
2d4bdee
Model Deploy tasks parameters in tables
eedorenko Aug 16, 2019
c0860e5
tables with task parameters uopdate
eedorenko Aug 16, 2019
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
minor add and typo fix
  • Loading branch information
David Tesar
David Tesar authored Aug 16, 2019
commit c8c282430d7266a1e620e0fba5cafb0ecd1c67f8
4 changes: 2 additions & 2 deletions docs/getting_started.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ Check out created resources in the [Azure Portal](portal.azure.com):

![created resources](./images/created-resources.png)

Alternatively, you can also use a [cleaning pipeline](../environment_setup/iac-remove-environment.yml) that removes resources ctreated for this project or you can just delete a resource group in the [Azure Portal](portal.azure.com).
Alternatively, you can also use a [cleaning pipeline](../environment_setup/iac-remove-environment.yml) that removes resources created for this project or you can just delete a resource group in the [Azure Portal](portal.azure.com).


### 6. Set up Build Pipeline
Expand Down Expand Up @@ -131,7 +131,7 @@ docker run -v $(System.DefaultWorkingDirectory)/_ci-build/mlops-pipelines/ml_se
mcr.microsoft.com/mlops/python:latest python run_train_pipeline.py
```

This release pipeline should be triggered whenever a new **ML training pipeline** is published by the **AzDo builder pipeline**. It can also be triggered manually or configured to run on a scheduled basis. Create a new release to trigger the pipeline manually:
This release pipeline should be automatically triggered (continuous deployment) whenever a new **ML training pipeline** is published by the **AzDo builder pipeline**. It can also be triggered manually or configured to run on a scheduled basis. Create a new release to trigger the pipeline manually:

![create release](./images/create-release.png)

Expand Down