Skip to content
This repository was archived by the owner on Sep 25, 2026. It is now read-only.

Update docs and pipeline status badge #303

Merged
Jenny So (j-so) merged 5 commits into from
Jul 7, 2020
Merged

Update docs and pipeline status badge #303

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
df4f678
docs
Jul 2, 2020
2b2fa4d
fix pipeline status badge and tf naming uniqueness
Jul 2, 2020
0a948fd
add a note about how to change the name of the pipeline
Jul 2, 2020
e2a9502
extra clarification on workspace connection
Jul 2, 2020
12d270f
Merge branch 'master' into jenns/docs
Jul 7, 2020
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
add a note about how to change the name of the pipeline
  • Loading branch information
j-so
j-so committed Jul 2, 2020
commit 0a948fd8168ede4499e0615dbefdd436f84644c2
18 changes: 17 additions & 1 deletion docs/getting_started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,9 +213,25 @@ In order to use these pipelines:

These pipelines rely on the model CI pipeline and reference it by name.

If you would like to change the name of your model CI pipeline, you must edit this section of yml for the CD and batch scoring pipeline, where it says `source: Model-Train-Register-CI` to use your own name.
```
trigger: none
resources:
containers:
- container: mlops
image: mcr.microsoft.com/mlops/python:latest
pipelines:
- pipeline: model-train-ci
source: Model-Train-Register-CI # Name of the triggering pipeline
trigger:
branches:
include:
- master
```

---

These pipelines have the following behaviors:
The release deployment and batch scoring pipelines have the following behaviors:

- The pipeline will **automatically trigger** on completion of the Model-Train-Register-CI pipeline for the master branch.
- The pipeline will default to using the latest successful build of the Model-Train-Register-CI pipeline. It will deploy the model produced by that build.
Expand Down