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.
You have an Azure DevOps project.
Your build process creates several artifacts.
You need to deploy the artifacts to on-premises servers.
Solution: You deploy an Azure self-hosted agent to an on-premises server. You add a Copy and Publish Build Artifacts task to the deployment pipeline.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.A
To build your code or deploy your software using Azure Pipelines, you need at least one agent.
If your on-premises environments do not have connectivity to a Microsoft-hosted agent pool (which is typically the case due to intermediate firewalls), you'll need to manually configure a self-hosted agent on on-premises computer(s). The agents must have connectivity to the target on-premises environments, and access to the Internet to connect to Azure Pipelines or Team Foundation Server.
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devopsYes, the proposed solution of deploying an Azure self-hosted agent to an on-premises server and adding a Copy and Publish Build Artifacts task to the deployment pipeline meets the goal of deploying artifacts to on-premises servers.
Here's why:
An Azure self-hosted agent is a software agent that runs on an on-premises machine and communicates with Azure DevOps to run build and release tasks. By deploying an Azure self-hosted agent to an on-premises server, you can use it to deploy artifacts to that server.
The Copy and Publish Build Artifacts task is a built-in task in Azure DevOps that copies build artifacts and publishes them to a file share, UNC path, or Azure Blob storage. By adding this task to the deployment pipeline, you can copy and publish the artifacts created by the build process to the on-premises server.
Together, the proposed solution allows you to deploy the artifacts to the on-premises servers using Azure DevOps. However, it's important to note that this solution assumes that the on-premises servers are accessible from the internet, as the Azure self-hosted agent communicates with Azure DevOps over the internet. If the on-premises servers are not accessible from the internet, alternative solutions may need to be considered, such as setting up a VPN connection or deploying an on-premises agent with direct connectivity to Azure DevOps.