Your company has a project in Azure DevOps.
You need to ensure that when there are multiple builds pending deployment, only the most recent build is deployed.
What should you use?
Click on the arrows to vote for the correct answer
A. B. C. D.B
The options you can choose for a queuing policy are:
-> Number of parallel deployments
-> If you specify a maximum number of deployments, two more options appear:
- Deploy all in sequence
- Deploy latest and cancel the others: Use this option if you are producing releases faster than builds, and you only want to deploy the latest build.
Incorrect Answers:
C: Release gates allow automatic collection of health signals from external services, and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/stages?tabs=classic&view=azure-devops#queuing-policiesThe correct answer to this question is B, deployment queue settings.
In Azure DevOps, the deployment queue is where build artifacts are stored while they wait to be deployed to a target environment. By default, the deployment queue allows multiple builds to be queued up for deployment. However, this can result in older builds being deployed instead of the most recent build.
To ensure that only the most recent build is deployed when there are multiple builds pending deployment, you can use the deployment queue settings to set the maximum number of builds that can be queued up for deployment at any given time. You can also set the maximum age of builds that are allowed in the deployment queue.
By setting the maximum number of builds to 1 and the maximum age to a short period of time, you can ensure that only the most recent build is deployed. This will prevent older builds from being deployed and potentially causing issues or bugs in the target environment.
Deployment conditions (Option A) can be used to specify conditions that must be met before a deployment can occur, such as the successful completion of a previous deployment. However, they do not address the issue of multiple builds pending deployment.
Release gates (Option C) are a type of automated quality check that can be used to prevent a release from being deployed if certain conditions are not met. While release gates can be useful for ensuring that deployments meet specific criteria, they are not directly related to the issue of multiple builds pending deployment.
Pull request triggers (Option D) are used to automatically trigger a build or deployment when a pull request is created or updated. While pull request triggers can be useful for automating the deployment process, they do not address the issue of multiple builds pending deployment.