Automating Build Process in Azure DevOps
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 Pre-deployment conditions settings of the release pipeline, you select Batch changes while a build is in progress.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B
Instead, In Visual Designer you enable continuous integration (CI) by:
1. Select the Triggers tab.
2. Enable Continuous integration.
https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-designerThe provided solution is incorrect, and the answer is B. No.
The reason is that the solution mentioned in the question is referring to the "Pre-deployment conditions" of the "Release" pipeline, whereas the goal is to ensure that a build runs automatically when code is checked in.
In this case, the correct solution would be to configure a Continuous Integration (CI) build pipeline that triggers automatically when code is checked into the repository. To do this, you can follow these steps:
Go to the Azure DevOps project and navigate to the project repository where the code is stored.
Click on the "Set up build" button in the top-right corner of the repository.
Choose the appropriate template for your application type. For example, if it's a .NET application, choose the ".NET Desktop" template.
Configure the build pipeline settings such as the build agent, triggers, and other build steps based on the project requirements.
Save the pipeline and test it by checking in some code changes to the repository.
After configuring the build pipeline, it will trigger automatically when code is checked into the repository, and the build will run to compile, test, and package the application. This approach ensures that the build process is automated, and code changes are tested early and frequently to catch any issues early in the development cycle.
In conclusion, selecting the "Batch changes while a build is in progress" option in the release pipeline's pre-deployment conditions will not achieve the goal of automatically triggering a build when code is checked in. Therefore, the answer is No.
