From the course: Developing CI/CD Solutions with Azure DevOps
Unlock the full course today
Join today to access over 24,700 courses taught by industry experts.
Simulate CI trigger and branching policies - Azure Tutorial
From the course: Developing CI/CD Solutions with Azure DevOps
Simulate CI trigger and branching policies
- [Instructor] We now have a working build pipeline, defined by using a task group: enabled continuous integration on the main and feature branches, and also enabled branching policies to require a pull request with a successful PR build before pulling changes into the main branch. Now, let's simulate a typical situation where a developer needs to modify code in a feature branch and merge with the main branch. Remember, earlier in the scan result of SonarCloud, we have a bug with a suggested solution to add a description to the table. Let's try to fix that locally in Visual Studio Code, and then push to the remote repo. to see what happens when a developer push changes. In your student app project, navigate to repos. on the left menu, and then click on the clone button at the right side of the page. Let's copy this URL. Open a terminal in your system. I have my batch terminal opened already, so I'll navigate to…
Contents
-
-
-
-
(Locked)
Get your source code to Azure Repos2m 56s
-
(Locked)
Configure a build pipeline11m 22s
-
(Locked)
Integrate SonarCloud with the build pipeline13m 16s
-
(Locked)
Protect your important branches8m 35s
-
(Locked)
Create a task group for build pipelines9m 47s
-
(Locked)
Simulate CI trigger and branching policies9m 30s
-
(Locked)
-
-
-