fixing pipeline condition (microsoft#209)

Fixing regression introduced in microsoft#207 - don't continue pipeline on lint/unit test errors.

Enable deploy of model registered by previous build (microsoft#207)

Allows you to skip the first two stages of the pipeline and deploy a model registered by a previous build by setting the variable MODEL_BUILD_ID to the previous build's id when queuing the pipeline. This speeds up the process of fixing issues with the scoring or deployment configuration.

fix hard coded subscription reference (microsoft#205)

Remove 60 minute job timeout microsoft#203

Use correct parameter names in web app deploy (microsoft#202)

Clarify that web app must exist for the deploy to work (microsoft#201)

Add basic descriptions to YAML pipelines (microsoft#200)

* Add basic descriptions to YAML pipelines

* Updated comments to address review feedback

* Add missing feedback fix

fix model input features (microsoft#198)

Co-authored-by: Eugene Fedorenko <eugene.fedor@gmail.com>

Getting started refactoring (microsoft#197)

* State explicitly the flow order (Template as it is with Diabetes-> Bootstrap with your project code)
* Fix “multistage pipeline structure” explanation
* Clarify the R approach. It has only the model training. There is no evaluation/registration
* Fix the confusion with AzureResourceConnection and WORKSPACE_SVC_CONNECTION
* Explain using of a Docker image in the pipeline
* Link to bring-your-own-code (Bryan’s) article
* Fix broken links (e.g. diabetes_regression-ci-build-train.yml)
* Provide ML Service connection screenshot
* Explain explicit "diabetes" names. (e.g. The repo contains a sample “diabetes regression” project so here and there all names contain "diabetes")
* Clarify the folder structure (Common folders (e.g. .pipelines, ml_service) vs Project folders (e.g. diabetes_regression))

run unit tests in any case (microsoft#199)