Bash<\/strong>.<\/li><\/ul>\n\n\n\nNote<\/strong>: If this is the first time you are starting Cloud Shell<\/strong> and you are presented with the You have no storage mounted<\/strong> message, select the subscription you are using in this lab, and select Create storage<\/strong>.<\/p>\n\n\n\nFrom the\u00a0Bash<\/strong>\u00a0prompt, in the\u00a0Cloud Shell<\/strong>\u00a0pane, run the following command to create a resource group (replace the\u00a0<region>\u00a0placeholder with the name of the Azure region closest to you such as \u2018eastus\u2019).<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
LOCATION='eastus'<\/code><\/pre>\n\n\n\nCodeCopy<\/p>\n\n\n\n
RESOURCEGROUPNAME='exceedm11l01-RG'\naz group create --name $RESOURCEGROUPNAME --location $LOCATION\n<\/code><\/pre>\n\n\n\nTo create a Windows App service plan by running the following command:<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
SERVICEPLANNAME='exceedl11a-sp1'\naz appservice plan create --resource-group $RESOURCEGROUPNAME --name $SERVICEPLANNAME --sku B3\n<\/code><\/pre>\n\n\n\nNote<\/strong>: If the\u00a0az appservice plan create\u00a0command fails with an error message starting with\u00a0ModuleNotFoundError: No module named ‘vsts_cd_manager’, then run the following commands and then re-run the failed command.<\/p>\n\n\n\nCodeCopy<\/p>\n\n\n\n
az extension remove -n appservice-kube\naz extension add --yes --source \"https:\/\/aka.ms\/appsvc\/appservice_kube-latest-py2.py3-none-any.whl\"\n<\/code><\/pre>\n\n\n\nCreate a web app with a unique name.<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
WEBAPPNAME=partsunlimited$RANDOM$RANDOM\naz webapp create --resource-group $RESOURCEGROUPNAME --plan $SERVICEPLANNAME --name $WEBAPPNAME\n<\/code><\/pre>\n\n\n\nNext, create an Azure SQL Server.<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
USERNAME=\"Student\"\nSQLSERVERPASSWORD=\"Pa55w.rd1234\"\nSERVERNAME=\"partsunlimitedserver$RANDOM\"\n\naz sql server create --name $SERVERNAME --resource-group $RESOURCEGROUPNAME \\\n--location $LOCATION --admin-user $USERNAME --admin-password $SQLSERVERPASSWORD\n<\/code><\/pre>\n\n\n\nThe web app needs to be able to access the SQL server, so we need to allow access to Azure resources in the SQL Server firewall rules.<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
STARTIP=\"0.0.0.0\"\nENDIP=\"0.0.0.0\"\naz sql server firewall-rule create --server $SERVERNAME --resource-group $RESOURCEGROUPNAME \\\n--name AllowAzureResources --start-ip-address $STARTIP --end-ip-address $ENDIP\n<\/code><\/pre>\n\n\n\nNow create a database within that server.<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
az sql db create --server $SERVERNAME --resource-group $RESOURCEGROUPNAME --name PartsUnlimited --service-objective S0\n<\/code><\/pre>\n\n\n\nThe web app you created needs the database connection string in its configuration, so run the following commands to prepare and add it to the app settings of the web app.<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
CONNSTRING=$(az sql db show-connection-string --name PartsUnlimited --server $SERVERNAME \\\n--client ado.net --output tsv)\n\nCONNSTRING=${CONNSTRING\/\/<username>\/$USERNAME}\nCONNSTRING=${CONNSTRING\/\/<password>\/$SQLSERVERPASSWORD}\n\naz webapp config connection-string set --name $WEBAPPNAME --resource-group $RESOURCEGROUPNAME \\\n-t SQLAzure --settings \"DefaultConnectionString=$CONNSTRING\" \n<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
Lab 1: Configure CI\/CD Pipelines as Code with YAML in Azure DevOps<\/strong><\/p>\n\n\n\nIn this Lab, you will configure CI\/CD Pipelines as code with YAML in Azure DevOps.<\/p>\n\n\n\n
Task 1: Delete the existing pipeline<\/strong><\/p>\n\n\n\nIn this task, you will delete the existing pipeline.<\/p>\n\n\n\n
On the lab computer, switch to the browser window displaying the\u00a0Configuring Pipelines as Code with YAML<\/strong>\u00a0project in the Azure DevOps portal and, in the vertical navigational pane, select the\u00a0Pipelines<\/strong>.<\/li><\/ul>\n\n\n\nNote<\/strong>: Before configuring YAML pipelines, you will disable the existing build pipeline.<\/p>\n\n\n\nOn the\u00a0Pipelines<\/strong>\u00a0pane, select the\u00a0PartsUnlimited<\/strong>\u00a0entry.<\/li>In the upper right corner of the\u00a0PartsUnlimited<\/strong>\u00a0blade, click the vertical ellipsis symbol and, in the drop-down menu, select\u00a0Delete<\/strong>.<\/li><\/ul>\n\n\n\nWrite\u00a0PartsUnlimited<\/strong>\u00a0and click\u00a0Delete<\/strong>.<\/p>\n\n\n\n<\/p>\n\n\n\n
In the vertical navigational pane, select the\u00a0Repos > Files<\/strong>. Make sure you are in the\u00a0master<\/strong>\u00a0branch (dropdown on top of\u00a0Files<\/strong>\u00a0window), on the\u00a0azure-pipelines.yml<\/strong>\u00a0file, click the vertical ellipsis symbol and, in the drop-down menu, select\u00a0Delete<\/strong>. Commit the change on the master branch by clicking on\u00a0Commit<\/strong>\u00a0(leaving default options).<\/p>\n\n\n\n<\/p>\n\n\n\n
Task 2: Add a YAML build definition<\/strong><\/p>\n\n\n\nIn this task, you will add a YAML build definition to the existing project.<\/p>\n\n\n\n
Navigate back to the\u00a0Pipelines<\/strong>\u00a0pane in of the\u00a0Pipelines<\/strong>\u00a0hub.<\/li>In the\u00a0Create your first Pipeline<\/strong>\u00a0window, click\u00a0Create pipeline<\/strong>.<\/li><\/ul>\n\n\n\n<\/p>\n\n\n\n
Note<\/strong>: We will use the wizard to automatically create the YAML definition based on our project.<\/p>\n\n\n\nOn the\u00a0Where is your code?<\/strong>\u00a0pane, click\u00a0Azure Repos Git (YAML)<\/strong>\u00a0option.<\/li><\/ul>\n\n\n\nOn the\u00a0Select a repository<\/strong>\u00a0pane, click\u00a0PartsUnlimited<\/strong>.<\/p>\n\n\n\nOn the\u00a0Configure your pipeline<\/strong>\u00a0pane, click **ASP.NET** to use this template as the starting point for your pipeline. This will open the **Review your pipeline YAML** pane.<\/p>\n\n\n\n<\/p>\n\n\n\n
Note<\/strong>: The pipeline definition will be saved as a file named\u00a0azure-pipelines.yml<\/strong>\u00a0in the root of the repository. The file will contain the steps required to build and test a typical ASP.NET solution. You can also customize the build as needed. In this scenario, you will update the **pool** to enforce the use of a VM running Windows 2019.<\/p>\n\n\n\nMake sure\u00a0trigger\u00a0is\u00a0master<\/strong>.<\/li><\/ul>\n\n\n\nNote<\/strong>: Review in Repos if your repository has master<\/strong> or main<\/strong> branch, organizations could choose default branch name for new repos: Change the default branch<\/a>.<\/p>\n\n\n\nOn the\u00a0Review your pipeline YAML<\/strong>\u00a0pane, in line\u00a010<\/strong>, replace\u00a0vmImage: ‘windows-latest’\u00a0with\u00a0vmImage: ‘windows-2019’.<\/li>Remove the\u00a0VSTest@2<\/strong>\u00a0task: “`yamltask: VSTest@2 inputs: platform: \u2018$(buildPlatform)\u2019 configuration: \u2018$(buildConfiguration)\u2019 “`<\/li><\/ul><\/li> On the\u00a0Review your pipeline YAML<\/strong>\u00a0pane, click\u00a0Save and run<\/strong>.<\/li>On the\u00a0Save and run<\/strong>\u00a0pane, accept the default settings and click\u00a0Save and run<\/strong>.<\/li><\/ul>\n\n\n\nOn the pipeline run pane, in the\u00a0Jobs<\/strong>\u00a0section, click\u00a0Job<\/strong>\u00a0and monitor its progress and verify that it completes successfully.<\/p>\n\n\n\n<\/p>\n\n\n\n
Note<\/strong>: Each task from the YAML file is available for review, including any warnings and errors.<\/p>\n\n\n\nTask 3: Add continuous delivery to the YAML definition<\/strong><\/p>\n\n\n\nIn this task, you will add continuous delivery to the YAML-based definition of the pipeline you created in the previous task.<\/p>\n\n\n\n
Note<\/strong>: Now that the build and test processes are successful, we can now add delivery to the YAML definition.<\/p>\n\n\n\nOn the pipeline run pane, click the ellipsis symbol in the upper right corner and, in the dropdown menu, click\u00a0Edit pipeline<\/strong>.<\/li>On the pane displaying the content of the\u00a0azure-pipelines.yaml<\/strong>\u00a0file, in line\u00a08<\/strong>, following the\u00a0trigger\u00a0section, add the following content to define the\u00a0Build<\/strong>\u00a0stage in the YAML pipeline.<\/li><\/ul>\n\n\n\nNote<\/strong>: You can define whatever stages you need to better organize and track pipeline progress.<\/p>\n\n\n\nCodeCopy<\/p>\n\n\n\n
stages:\n- stage: Build\n jobs:\n - job: Build\n<\/code><\/pre>\n\n\n\nSelect the remaining content of the YAML file and press the\u00a0Tab<\/strong>\u00a0key twice to indent it four spaces (it should be placed with same identation as\u00a0job: Build).<\/li><\/ul>\n\n\n\nNote<\/strong>: This way, everything starting with the pool section becomes part of the job: Build.<\/p>\n\n\n\nAt the bottom of the file, add the configuration below to define the second stage.<\/li><\/ul>\n\n\n\nCodeCopy<\/p>\n\n\n\n
- stage: Deploy\n jobs:\n - job: Deploy\n pool:\n vmImage: 'windows-2019'\n steps:\n<\/code><\/pre>\n\n\n\nSet the cursor on a new line at the end of the YAML definition.<\/li><\/ul>\n\n\n\nNote<\/strong>: This will be the location where new tasks are added.<\/p>\n\n\n\nIn the list of tasks on the right side of the code pane, search for and select the\u00a0Azure App Service Deploy<\/strong>\u00a0task.<\/li>In the\u00a0Azure App Service deploy<\/strong>\u00a0pane, specify the following settings and click\u00a0Add<\/strong>:in the\u00a0Azure subscription<\/strong>\u00a0drop-down list, select the Azure subscription into which you deployed the Azure resources earlier in the lab, click\u00a0Authorize<\/strong>, and, when prompted, authenticate by using the same user account you used during the Azure resource deployment.<\/li>in the\u00a0App Service name<\/strong>\u00a0dropdown list, select the name of the web app you deployed earlier in the lab.<\/li>in the\u00a0Package or folder<\/strong>\u00a0text box, type\u00a0$(System.ArtifactsDirectory)\/drop\/*.zip.<\/li><\/ul><\/li><\/ul>\n\n\n\nNote<\/strong>: This will automatically add the deployment task to the YAML pipeline definition.<\/p>\n\n\n\nWith the added task still selected in the editor, press the\u00a0Tab<\/strong>\u00a0key twice to indent it four spaces, so that it listed as a child of the\u00a0steps<\/strong>\u00a0task.<\/li><\/ul>\n\n\n\nNote<\/strong>: The packageForLinux<\/strong> parameter is misleading in the context of this lab, but it is valid for Windows or Linux.<\/p>\n\n\n\nNote<\/strong>: By default, these two stages run independently. As a result, the build output from the first stage might not be available to the second stage without additional changes. To implement these changes, we will use one task to publish the build output at the end of the build stage and another to download it in the beginning of the deploy stage.<\/p>\n\n\n\nPlace the cursor on a blank line at the end of the build stage to add another task. (right below\u00a0task: VSBuild@1\u00a0)<\/li> On the\u00a0Tasks<\/strong>\u00a0pane, search for and select the\u00a0
![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture1-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture2-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture3-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture4-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture5-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture6-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture7-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture8-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture9-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture10-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture11-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture12-8.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture13-7.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture14-6.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture15-7.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture16-6.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture17-6.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture18-6.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/exceedthecloud.com\/wp-content\/uploads\/2022\/04\/Picture19-5.png\")
<\/figure>\n\n\n\n