Enable Continuous Integration for Automatic Build Triggering
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
Your company has a project in Azure DevOps for a new web application.
You need to ensure that when code is checked in, a build runs automatically.
Solution: From the Triggers tab of the build pipeline, you select Enable continuous integration.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.A
In Visual Designer you enable continuous integration (CI) by:
1. Select the Triggers tab.
2. Enable Continuous integration.
A continuous integration trigger on a build pipeline indicates that the system should automatically queue a new build whenever a code change is committed.
https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-designerYes, the given solution meets the goal of automatically triggering a build when code is checked in.
Explanation:
Continuous Integration (CI) is a DevOps practice where developers integrate their code changes into a shared repository frequently, ideally several times a day. Every time a change is made, the code is built and tested automatically to detect any issues early in the development cycle.
In Azure DevOps, a build pipeline is a series of steps that builds and tests the code every time there is a code change. You can configure a build pipeline to trigger automatically whenever code is checked in, using the Triggers tab of the pipeline.
The given solution is to enable continuous integration from the Triggers tab of the build pipeline. This means that whenever code is checked in, the build pipeline will be triggered automatically, and the code will be built and tested. This meets the goal of ensuring that a build runs automatically when code is checked in.
Therefore, the correct answer is A. Yes.
