Intial commit, fixing some of the bugs found in the getting started guide

Author: jainr

docs/getting_started.md

@@ -82,44 +82,63 @@ Great, you now have the build pipeline setup, you can either manually trigger it
 
 **Note:** For setting up release pipelines, first download the [release-pipelines](../release-pipelines) to your local filesystem so you can import it.
 
-1. Select the Release tab from the menu on the left, then click on **New Pipeline**![import release pipeline](./images/release-new-pipeline.png)
+**Also Note:** If this is the first time you are creating a release pipeline, you would see the following option, click on **New Pipeline**
+![import release pipeline](./images/release-new-pipeline.png)
 
-2. <<TODO: Create a empty release pipeline definition, such that we can get option to import the pipeline Json>>
+To enable the option to **Import release pipeline**, we must have atleast one release pipeline so let's create one with an empty job.
+![import release pipeline](./images/release-empty-job.png)
 
-2. Select the Release tab from the menu on the left, then click the New dropdown on top and click on **Import Release pipeline**
+On the next screen, click on **Save** and then click **Ok** to save the empty release pipeline.
+![import release pipeline](./images/release-save-empty.png)
+
+**Steps**
+
+1. Select the Release tab from the menu on the left, then click the New dropdown on top and click on **Import Release pipeline**
 ![import release pipeline](./images/release-import.png)
 
-3. On the next screen, navigate to release-pipelines folder and select retrainingtrigger.json pipeline file, click import. You should now see the following screen. Under Stages click on the Retrain stage, where it shows the red error sign.
+1. On the next screen, navigate to release-pipelines folder and select retrainingtrigger.json pipeline file, click import. You should now see the following screen. Under Stages click on the Retrain stage, where it shows the red error sign.
 ![release retraining triggger](./images/release-retrainingtrigger.png)
 
-   Click on agent job and then from the drop down for Agent Pool on the right side select **Hosted Ubuntu 1604** agent to execute your run and click **Save** button on top right.
+    Click on agent job and then from the drop down for Agent Pool on the right side select **Hosted Ubuntu 1604** agent to execute your run and click **Save** button on top right.
 ![release retraining agent](./images/release-retrainingagent.png)
 
-4. We want the retraining pipeline to be triggered every time build pipeline is complete. To create this dependency, we will link the artifact from build pipeline as a trigger for retraining trigger release pipeline. To do so, click on the pipeline tab and then hit **Add an artifact** option under Artifacts.
+1. We would now link the variable group we created earlier to this release pipeline. To do so click on the **Variables** tab, then click on **Variable** groups and then select **Link variable group** and select the variable group that we created in previous step and click **Link** followed by **Save** button.
+![release retraining artifact](./images/release-link-vg.png)
+1. We want the retraining pipeline to be triggered every time build pipeline is complete. To create this dependency, we will link the artifact from build pipeline as a trigger for retraining trigger release pipeline. To do so, click on the **pipeline** tab and then select **Add an artifact** option under Artifacts.
 ![release pipeline view](./images/release-retrainingpipeline.png)
 
-5. This will open up a pop up window, on this screen:
+1. This will open up a pop up window, on this screen:
     - for source type, select **Build**
     - for project, select your project in Azure DevOps that you created in previous steps.
     - For Source select the source build pipeline.
     - Other fields will get auto populated, you can leave them as it is.
   ![release retraining artifact](./images/release-retrainingartifact.png)
 
-6. Artifact is now added for retraining trigger pipeline, hit the **save** button on top right and then click **ok**. You now have the retraining trigger pipeline all set up and it will get executed everytime your build pipeline finishes its run. If you want to run this pipeline on a schedule, you can set one by clicking on **Schedule set** in Artifacts section.
+1. Artifact is now added for retraining trigger pipeline, hit the **save** button on top right and then click **ok**. You now have the retraining trigger pipeline all set up. To trigger this pipeline every time build pipeline executes, click on the lighting sign to enable the **Continous Deployment Trigger**, click Save.
+    ![release retraining artifact](./images/release-deploymentcitrigger.png)
+   
+1. We now need to update one of the tasks in the pipeline to correct the script path as it is dependent on the artifact name. The artifact name is based of your GitHub username since you cloned the repo. To make the change
+     - From the release pipeline view, click on the highlighted section.
+  ![release retraining task](./images/release-retraintask.png)
+     -  On the next screen, select the **install requirements** task and click on three dots in the highlighted section.
+  ![release env task](./images/release-envtask.png).
+      - This will open a pop up for the linked artifact and you can select the file.
+  ![release env task](./images/release-envtask-scriptpath.png)
+    Also update the path for **Working Directory** (under Advanced) and select **environment_setup** as working directoy from the linked artifact.
+     - Similarly for **Run AML Pipeline** task, change the working directory to **devops-for-ai** under your artifact.
+  ![release env task](./images/release-workingdir.png)
+   
+2. If you want to run this pipeline on a schedule, you can set one by clicking on **Schedule set** in Artifacts section.
 ![release retraining artifact](./images/release-retrainingartifactsuccess.png)
 
-1. <<TODO: Link Variable group to the release pipeline>>
-
-7. You can also run this pipeline on a schedule. Click on **Schedule set** to set the pipeline run schedule
-
-
-To view the newly created pipeline, click on the release tab on the left hand side and it will show the retraining trigger pipeline.
-
-1. <<TODO: Enable the continuous deployment trigger on the build artifact>>
-
-1. <<TODO: Manual Trigger the retraining pipeline trigger>>
+1. For the first time, we will manually trigger this pipeline.
+   - Click Releases option on the left hand side and navigate to the release pipeline you just created.
+  ![release retraining artifact](./images/release-createarelease.png)
+   - Click **Create Release**
+  ![release create ](./images/release-create.png)
+   - On the next screen click on **Create** button, this creates a manual release for you.
 
-1. <<TODO: The artifact name is defined by the name of build pipeline. If people fork it, the build pipeline name will change, this will change the artifact name and the workingDirectory path will change causing release pipelines to fail >>
+2. <<TODO: The artifact name is defined by the name of build pipeline. If people fork it, the build pipeline name will change, this will change the artifact name and the workingDirectory path will change causing release pipelines to fail >>
 
 ### 7. Set up release (Deployment) pipeline
 

release-pipelines/retrainingtrigger.json

@@ -151,10 +151,10 @@
                             "condition": "succeeded()",
                             "inputs": {
                                 "targetType": "filePath",
-                                "filePath": "$(System.DefaultWorkingDirectory)/_Microsoft.DevOpsForAI/devops-for-ai/environment_setup/install_requirements.sh",
+                                "filePath": "$(System.DefaultWorkingDirectory)",
                                 "arguments": "",
                                 "script": "# Write your commands here\n\n# Use the environment variables input below to pass secret variables to this script",
-                                "workingDirectory": "$(System.DefaultWorkingDirectory)/_Microsoft.DevOpsForAI/devops-for-ai/environment_setup",
+                                "workingDirectory": "$(System.DefaultWorkingDirectory)",
                                 "failOnStderr": "false",
                                 "noProfile": "true",
                                 "noRc": "true"
@@ -194,7 +194,7 @@
                             "condition": "succeeded()",
                             "inputs": {
                                 "script": "python aml_service/05-TriggerAmlPipeline.py",
-                                "workingDirectory": "$(System.DefaultWorkingDirectory)/_Microsoft.DevOpsForAI/devops-for-ai",
+                                "workingDirectory": "$(System.DefaultWorkingDirectory)",
                                 "failOnStderr": "false"
                             }
                         }