From the course: Visual Studio Tools for Azure DevOps
Unlock the full course today
Join today to access over 22,700 courses taught by industry experts or purchase this course individually.
Use git push to trigger Azure Pipelines
From the course: Visual Studio Tools for Azure DevOps
Use git push to trigger Azure Pipelines
- [Instructor] On the right is the project in Visual Studio. There is one change here in this index.cs HTML file. On the left, I have the browser which has two tabs. The first tab shows the currently deployed site. After a successful deploy, we should see the version number and title change. The second tab shows the Azure Pipelines page on the DevOps sites. We'll look at this in more detail soon. For this demo, I have it on screen so you can see the build process start when I commit the code changes. Over in Visual Studio, I'll Commit All and Push. Maximize the browser so you can see that the build has started. On the Pipelines site, the build has been triggered. We can see the new build number and the build progress on the page. For this simple change, the build and deploy process takes less than a minute. Now that Azure Pipelines is finished, let's switch over to the first tab and reload the page. We'll verify that the title changed and the version number changed too. The only part…
Contents
-
-
-
-
-
-
(Locked)
What are Azure Pipelines?5m 10s
-
(Locked)
Examine the dev and deployed version of the example app1m 8s
-
(Locked)
Use git push to trigger Azure Pipelines1m 16s
-
(Locked)
Tour the CI/CD parts on the DevOps site3m 26s
-
(Locked)
Publish an existing web app to Azure App Service2m 21s
-
(Locked)
Publish an existing web app to Azure Pipelines1m 35s
-
(Locked)
Use a pull request to trigger Azure Pipelines2m
-
(Locked)
-