fixing demo generator links (#69)
This commit is contained in:
Sachin Raj
GitHub
Родитель
fa32fd9135
Коммит
be0239ceb4
|
|
@ -24,7 +24,7 @@ ASP.NET is an open source web framework for building modern web applications and
|
|||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=PartsUnlimited) to provision the team project on the VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ The Deployment Group installs a deployment agent on each of the target servers i
|
|||
|
||||
### What's covered in this lab
|
||||
|
||||
This lab covers the configuration of the deployment groups and details how the deployment groups could be used in VSTS Release management.
|
||||
This lab covers the configuration of the deployment groups and details how the deployment groups could be used in VSTS Release management.
|
||||
|
||||
### Prerequisites for the lab
|
||||
|
||||
|
|
@ -64,9 +64,9 @@ The following resources will be provisioned on the Azure using an ARM template:
|
|||
|
||||
## Setting up the VSTS team project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=PartsUnlimited) to provision the team project on the VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=deploymentgroups&TemplateId=77368) to provision the team project on the VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -85,9 +85,9 @@ The below diagram details the VSTS DevOps workflow with Docker:
|
|||
|
||||
## Setting up the VSTS Project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=PartsUnlimited) to provision the team project on the VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=Docker&TemplateId=77363) to provision the team project on the VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,13 +9,13 @@ This lab shows how to deploy an ASP.NET Core application to Azure App Service wi
|
|||
- Deploy to the cloud or on-premises
|
||||
- Run on .NET Core or .NET Framework.
|
||||
|
||||
### Prerequisites for the lab
|
||||
## Prerequisites for the lab
|
||||
|
||||
1. **Microsoft Azure Account**: You will need a valid and active Azure account for the Azure labs. If you do not have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/){:target="_blank"}
|
||||
|
||||
* If you are an active Visual Studio Subscriber, you are entitled for a $50-$150 credit per month. You can refer to this [link](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/){:target="_blank"} to find out more information about this including how to activate and start using your monthly Azure credit.
|
||||
- If you are an active Visual Studio Subscriber, you are entitled for a $50-$150 credit per month. You can refer to this [link](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/){:target="_blank"} to find out more information about this including how to activate and start using your monthly Azure credit.
|
||||
|
||||
* If you are not a Visual Studio Subscriber, you can sign up for the FREE [Visual Studio Dev Essentials](https://www.visualstudio.com/dev-essentials/){:target="_blank"} program to create a **Azure free account** (includes 1 year of free services, $200 for 1st month).
|
||||
- If you are not a Visual Studio Subscriber, you can sign up for the FREE [Visual Studio Dev Essentials](https://www.visualstudio.com/dev-essentials/){:target="_blank"} program to create a **Azure free account** (includes 1 year of free services, $200 for 1st month).
|
||||
|
||||
1. You will need a **Visual Studio Team Services Account**. If you do not have one, you can sign up for free [here](https://www.visualstudio.com/products/visual-studio-team-services-vs){:target="_blank"}
|
||||
|
||||
|
|
@ -25,9 +25,9 @@ This lab shows how to deploy an ASP.NET Core application to Azure App Service wi
|
|||
|
||||
## Setting up the VSTS Project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=PartsUnlimited) to provision the team project on the VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net) to provision the team project on the VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
@ -39,9 +39,9 @@ This lab shows how to deploy an ASP.NET Core application to Azure App Service wi
|
|||
|
||||
Since the connections are not established during project provisioning, we will manually create the endpoints.
|
||||
|
||||
In VSTS, navigate to **Services** by clicking the gear icon , and click **+ New Service Endpoint**. Select **Azure Resource Manager**. Specify **Connection name**, select your **Subscription** from the dropdown and click **OK**. We use this endpoint to connect **VSTS** with **Azure**.
|
||||
In VSTS, navigate to **Services** by clicking the gear icon , and click **+ New Service Endpoint**. Select **Azure Resource Manager**. Specify **Connection name**, select your **Subscription** from the dropdown and click **OK**. We use this endpoint to connect **VSTS** with **Azure**.
|
||||
|
||||
|
||||
|
||||
|
||||
You will be prompted to authorize this connection with Azure credentials. Disable pop-up blocker in your browser if you see a blank screen after clicking OK, and retry the step.
|
||||
|
||||
|
|
@ -49,45 +49,45 @@ In VSTS, navigate to **Services** by clicking the gear icon 
|
|||
|
||||
Now that connections are established, we will manually map the endpoints to release definition.
|
||||
|
||||
> **Note** : You will encounter an error - **TFS.WebApi.Exception: Page not found** for Azure tasks in the release definition. This is due to a recent change in the VSTS Release Management API. While we are working on updating VSTS Demo Generator to resolve this issue, you can fix this by typing a random text in the **Azure Subscription** field and click the **Refresh** icon next to it. Once the field is refreshed, you can select the endpoint from the drop down.
|
||||
{% include warning.html content= "You will encounter an error - **TFS.WebApi.Exception: Page not found** for Azure tasks in the release definition. This is due to a recent change in the VSTS Release Management API. While we are working on updating VSTS Demo Generator to resolve this issue, you can fix this by typing a random text in the **Azure Subscription** field and click the **Refresh** icon next to it. Once the field is refreshed, you can select the endpoint from the drop down." %}
|
||||
|
||||
1. Go to **Releases** under **Build & Release** tab, edit the release definition **MyHealthClinicE2E**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select **Tasks** and click **Dev**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under **Azure Resource Group Deployment** task, update **Azure subscription** with the endpoint components from the dropdown and select the desired **location**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under **Azure App Service Deploy** task, update **Azure subscription** with the endpoint components from the dropdown. Under the **Slot** section enter the slot name as **Dev**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Similarly update **Azure subscription** with the endpoint components for **QA** and **Production** environments. Go to **Tasks** and select **QA**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under **Azure App Service Deploy** task, update **Azure subscription** with the endpoint components from the dropdown. Under the **Slot** section enter the slot name as **Staging**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Go to **Tasks** and select **Production**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under **Azure App Service Deploy** task, update **Azure subscription** with the endpoint components from the dropdown and click **Save** to save the release definition.
|
||||
|
||||
|
||||
|
||||
|
||||
## Exercise 3: Triggering a Continuous Integration (CI) build
|
||||
|
||||
1. Go to the **Code** hub.
|
||||
|
||||
|
||||
|
||||
|
||||
1. We have a **DOTNETCORE** app code provisioned by the demo generator system. We will deploy this to Azure app service.
|
||||
|
||||
|
|
@ -97,42 +97,42 @@ Now that connections are established, we will manually map the endpoints to rele
|
|||
|
||||
> **MyHealthClinic/src/MyHealth.Web/Views/Home/Index.cshtml**
|
||||
|
||||
|
||||
|
||||
|
||||
1. Edit the code. For this example, let's change **line 33** to change the text from **Login** to **Private Area**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select **Commit** to save and commit the changes.
|
||||
|
||||
1. The code commit will trigger the CI build. Go to the **Build** tab to see the CI build running in progress.
|
||||
|
||||
|
||||
|
||||
|
||||
While the build is in progress, let's explore the build definition. The tasks that is used in the build definition are listed in the table below.
|
||||
|
||||
|Tasks| Usage|
|
||||
|-----|------|
|
||||
| **Restore**| dotnet command-line tool restores all the package dependencies like **ASP.NET Core Identity, ASP.NET Core session** etc. required to build this project|
|
||||
| **npm Install**| npm task installs the npm packages (javascript dependencies) like **babelify, browserify** etc. required to build this project|
|
||||
| **Bower Install**|We will use this task to manage components that contain HTML, CSS, JavaScript, fonts and even image files. Example: jquery, angular, webcomponentsjs etc|
|
||||
| **Gulp**| gulp task compiles sass files, uglify and compress js files|
|
||||
| **Build**| We will use dotnet command-line tool to build the project and its dependencies into a set of binaries|
|
||||
| **Test**| dotnet command-line tool wil run unit tests as part of build process to ensure the code quality. This project contains 6 unit tests|
|
||||
| **Publish**| We will use this task to create a package with published content for the web deployment|
|
||||
| **Publish Test Results**| We will use this task to publish the unit test result|
|
||||
| **Copy Files**| We will copy the zipped file and the ARM template to a staging directory|
|
||||
| **Publish Build Artifacts**| And finally, we will publish the files in the staging directory which were copied in the previous step|
|
||||
| **Restore**| dotnet command-line tool restores all the package dependencies like **ASP.NET Core Identity, ASP.NET Core session** etc. required to build this project|
|
||||
| **npm Install**| npm task installs the npm packages (javascript dependencies) like **babelify, browserify** etc. required to build this project|
|
||||
| **Bower Install**|We will use this task to manage components that contain HTML, CSS, JavaScript, fonts and even image files. Example: jquery, angular, webcomponentsjs etc|
|
||||
| **Gulp**| gulp task compiles sass files, uglify and compress js files|
|
||||
| **Build**| We will use dotnet command-line tool to build the project and its dependencies into a set of binaries|
|
||||
| **Test**| dotnet command-line tool wil run unit tests as part of build process to ensure the code quality. This project contains 6 unit tests|
|
||||
| **Publish**| We will use this task to create a package with published content for the web deployment|
|
||||
| **Publish Test Results**| We will use this task to publish the unit test result|
|
||||
| **Copy Files**| We will copy the zipped file and the ARM template to a staging directory|
|
||||
| **Publish Build Artifacts**| And finally, we will publish the files in the staging directory which were copied in the previous step|
|
||||
|
||||
1. Click on the build number to open the live console.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. Once the build is complete click on the build number, to see the summary which shows **Test Results** as shown.
|
||||
|
||||
|
||||
|
||||
|
||||
## Exercise 4: Continuous Delivery
|
||||
|
||||
|
|
@ -142,15 +142,15 @@ We are using **Infrastructure as a Code** in the release pipeline. We have a rel
|
|||
|
||||
1. Select the **MyHealthClinicE2E** definition, you will see the release in-progress.
|
||||
|
||||
|
||||
|
||||
|
||||
1. While the release is in-progress, let's explore the tasks used. Click **edit** to see the release pipeline. We have three environments **Dev, QA** and **Production**.
|
||||
|
||||
|
||||
|
||||
|
||||
>Go to the Dev environment, you will see 2 tasks are used. Let us explore the tasks.
|
||||
|
||||
|
||||
|
||||
|
||||
- **Azure Resource Group Deployment**: The project used in this lab contains frontend (Azure App Service) and backend (Azure SQL DB) services. We will provision these services as PAAS on Azure using ARM templates. This task will create the above services in a resource group **dotnetcore.**
|
||||
|
||||
|
|
@ -158,21 +158,21 @@ We are using **Infrastructure as a Code** in the release pipeline. We have a rel
|
|||
|
||||
1. Click on **View releases**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Double click on the release to see the release summary.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. Login to [Azure Portal](https://portal.azure.com) and search a **Resource Group** with the name **dotnetcore**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Navigate to either Dev or Staging web app in the resource group and you will see the application is deployed successfully with the changes.
|
||||
|
||||
|
||||
|
||||
|
||||
## Summary
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ There are multiple ways to add code to a GitHub repository. We can start with a
|
|||
|
||||
## Setting up the VSTS team project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=PartsUnlimited) to provision the team project on the VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=GitHub&TemplateId=77366) to provision the team project on the VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -169,9 +169,9 @@ Since all the required azure components are now created, the VSTS team project c
|
|||
|
||||
## Setting up the VSTS team project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?TemplateId=77372&name=AKS){:target="_blank"} to provision the project on your VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=aks&templateId=77372){:target="_blank"} to provision the project on your VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create the team projects on your VSTS account with sample content that include source code, work items, iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create the team projects on your VSTS account with sample content that include source code, work items, iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -106,9 +106,9 @@ API key is used to authenticate VSTS with Octopus server. Using API key lets you
|
|||
|
||||
## Setting up the VSTS team project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?TemplateId=77370&name=octopus){:target="_blank"} to provision the project on our VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=octopus&TemplateId=77370){:target="_blank"} to provision the project on our VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -29,9 +29,9 @@ This lab shows how to deploy **PHP** application to **Azure App** service using
|
|||
|
||||
## Setting Up the VSTS Project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?TemplateId=77370&name=PHP&templateid=77365){:target="_blank"} to provision the project on our VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=PHP&TemplateId=77365){:target="_blank"} to provision the project on our VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ This lab shows how to deploy a **Python** application to **Azure App Service** f
|
|||
|
||||
## Setting Up the VSTS Project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=Python&templateid=77369){:target="_blank"} to provision a Python project on your VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=Python&TemplateId=77369){:target="_blank"} to provision a Python project on your VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,9 +20,9 @@ If you are not familiar with creating Selenium UI tests in Visual Studio, you ma
|
|||
|
||||
1. **Microsoft Azure Account**: You will need a valid and active Azure account for the Azure labs. If you do not have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/){:target="_blank"}
|
||||
|
||||
* If you are an active Visual Studio Subscriber, you are entitled for a $50-$150 credit per month. You can refer to this [link](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/){:target="_blank"} to find out more information about this including how to activate and start using your monthly Azure credit.
|
||||
- If you are an active Visual Studio Subscriber, you are entitled for a $50-$150 credit per month. You can refer to this [link](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/){:target="_blank"} to find out more information about this including how to activate and start using your monthly Azure credit.
|
||||
|
||||
* If you are not a Visual Studio Subscriber, you can sign up for the FREE [Visual Studio Dev Essentials](https://www.visualstudio.com/dev-essentials/){:target="_blank"} program to create a **Azure free account** (includes 1 year of free services, $200 for 1st month).
|
||||
- If you are not a Visual Studio Subscriber, you can sign up for the FREE [Visual Studio Dev Essentials](https://www.visualstudio.com/dev-essentials/){:target="_blank"} program to create a **Azure free account** (includes 1 year of free services, $200 for 1st month).
|
||||
|
||||
1. You will need a **Visual Studio Team Services Account**. If you do not have one, you can sign up for free [here](https://www.visualstudio.com/products/visual-studio-team-services-vs){:target="_blank"}
|
||||
|
||||
|
|
@ -42,11 +42,11 @@ If you are not familiar with creating Selenium UI tests in Visual Studio, you ma
|
|||
|
||||
## Setting up the VSTS team project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=Selenium&templateid=77367){:target="_blank"} to provision the project on your VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=Selenium&TemplateId=77367){:target="_blank"} to provision the project on your VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
{% include note.html content= "This URL will automatically select **Selenium** template in the demo generator. If you want to try other projects, use this URL instead -[https://vstsdemogenerator.azurewebsites.net/](https://vstsdemogenerator.azurewebsites.net/){:target=\"_blank\"}" %}
|
||||
|
||||
|
|
@ -80,8 +80,8 @@ In this exercise, we will execute the **registration script** on the VM to assoc
|
|||
|
||||
1. Login to the VM using [RDP](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/connect-logon){:target="_blank"} with the following credentials
|
||||
|
||||
* **Username**: vmadmin
|
||||
* **Password**: P2ssw0rd@123
|
||||
- **Username**: vmadmin
|
||||
- **Password**: P2ssw0rd@123
|
||||
|
||||
1. Open **Windows PowerShell** in **administrator** mode, paste the copied **Registration script** and hit **Enter**.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,9 +32,9 @@ In this lab, you will learn how to setup SonarQube on Azure and to integrate Vis
|
|||
|
||||
1. **Microsoft Azure Account**: You will need a valid and active Azure account for the Azure labs. If you do not have one, you can sign up for a [free trial](https://azure.microsoft.com/en-us/free/){:target="_blank"}
|
||||
|
||||
* If you are an active Visual Studio Subscriber, you are entitled for a $50-$150 credit per month. You can refer to this [link](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/){:target="_blank"} to find out more information about this including how to activate and start using your monthly Azure credit.
|
||||
- If you are an active Visual Studio Subscriber, you are entitled for a $50-$150 credit per month. You can refer to this [link](https://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits-details/){:target="_blank"} to find out more information about this including how to activate and start using your monthly Azure credit.
|
||||
|
||||
* If you are not a Visual Studio Subscriber, you can sign up for the FREE [Visual Studio Dev Essentials](https://www.visualstudio.com/dev-essentials/){:target="_blank"} program to create a **Azure free account** (includes 1 year of free services, $200 for 1st month).
|
||||
- If you are not a Visual Studio Subscriber, you can sign up for the FREE [Visual Studio Dev Essentials](https://www.visualstudio.com/dev-essentials/){:target="_blank"} program to create a **Azure free account** (includes 1 year of free services, $200 for 1st month).
|
||||
|
||||
1. You will need a **Visual Studio Team Services Account**. If you do not have one, you can sign up for free [here](https://www.visualstudio.com/products/visual-studio-team-services-vs){:target="_blank"}
|
||||
|
||||
|
|
@ -132,7 +132,7 @@ In this lab, you will learn how to setup SonarQube on Azure and to integrate Vis
|
|||
|
||||
## Exercise 2: Setting up the VSTS project
|
||||
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=SonarQube&templateid=77364){:target="_blank"} to provision a project on your VSTS account.
|
||||
1. Use the [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=SonarQube&TemplateId=77364){:target="_blank"} to provision a project on your VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
|
|
|||
|
|
@ -36,9 +36,9 @@ Team Services integration with WhiteSource Bolt will enable you to:
|
|||
|
||||
## Setting up the VSTS project
|
||||
|
||||
1. Use [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?name=WhiteSource%20Bolt&templateid=77362){:target="_blank"} to provision the WhiteSource project on your VSTS account.
|
||||
1. Use [VSTS Demo Generator](https://vstsdemogenerator.azurewebsites.net/?Name=WhiteSource%20Bolt&TemplateId=77362){:target="_blank"} to provision the WhiteSource project on your VSTS account.
|
||||
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
> **VSTS Demo Generator** helps you create team projects on your VSTS account with sample content that include source code, work items,iterations, service endpoints, build and release definitions based on the template you choose during the configuration.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче