Your company uses cloud-hosted Jenkins for builds.
You need to ensure that Jenkins can retrieve source code from Azure Repos.
Which three actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
To ensure Jenkins can retrieve source code from Azure Repos, you need to follow these steps: First, add the Team Foundation Server (TFS) plug-in to Jenkins, which provides compatibility and necessary functionality to interact with Azure Repos. Second, create a Personal Access Token (PAT) in your Azure DevOps account to serve as credentials for Jenkins to authenticate with Azure DevOps. Finally, add this PAT to your Jenkins account during the plug-in configuration to allow Jenkins to securely access the Azure Repos and retrieve source code as required.
I think B,D,E are right answers!
B,D,E https://devblogs.microsoft.com/devops/vsts-visual-studio-team-services-integration-with-jenkins/
Don't have token how to access?
Do not think is correct. B_C_D is. What you should configure a Webhook?
Why E? "You need to ensure that Jenkins can retrieve source code from Azure Repos." That's mean Jenkins access to Azure Repo, get the repo and run build. Not from Azure DevOps to trigger Jenkins 1. You need to install something at Jenkins to access Azure Repo --> B 2. Generate PAT at Azure Repo/DevOps --> D 3. Input this PAT at Jenkins to access the repo --> C
B,C,D (the given answer is correct) URL:https://docs.microsoft.com/en-us/azure/developer/jenkins/deploy-to-linux-vm-using-azure-devops-services by the way, webhook is used for Jenkins + Github, not for Azure Repos.
D. Create a personal access token (PAT) in your Azure DevOps account. (A PAT with read access to the Git repository is still needed for Jenkins to authenticate with Azure DevOps.) E. Create a service hook in Azure DevOps. (A service hook is crucial to trigger Jenkins builds upon relevant events in Azure DevOps.) C. Add the Team Foundation Server (TFS) plugin to Jenkins. (While Azure Repos is the current name for the service, the TFS plugin in Jenkins is still compatible and provides the necessary functionality to interact with Azure Repos and clone the source code.)
According with the documentation of the links: B D E https://learn.microsoft.com/es-es/azure/devops/service-hooks/services/jenkins?view=azure-devops https://azuredevopslabs.com/labs/vstsextend/jenkins/
CDE correct answer already tested in lab
CDE is Correct checked from Lab
https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins?view=azure-devops Here is shows PAT (D), PAT=API token in Jenkins (C) service hook in Azure DevOps (E)
CDE https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins?view=azure-devops
What should you configure as a Webhook?
Looks more accurate
E Definitely has to be part of the answer, see the link https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins?view=azure-devops
1) Create a PAT in ADO. 2) Create a service hook subscription in ADO. https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/jenkins/ 3) Add PAT to Jenkins. https://www.jenkins.io/doc/book/using/using-credentials/
Reference for B, D, E as below but it is 4 years ago. https://github.com/undergroundwires/Azure-in-bullet-points/blob/master/AZ-400%20Microsoft%20Azure%20DevOps%20Solutions/7.3.%20Jenkins.md
I agree with BCD. You do not need to create service hook in Az Devops because we are not triggerring any build. Here we need to Jenkins to access source code from Version control (TFS).
https://learn.microsoft.com/en-us/azure/developer/jenkins/deploy-to-linux-vm-using-azure-devops-services
I think B,C,D are correct. This question requires you to ensure that Jenkins can pull code from your repo (needs PAT + adding PAT to Jenkins + configure plugin) but does not ask to trigger the process after commits or whatever (service hook is not needed). There are more than 3 steps need to be taken in order to make things work. Ref: https://learn.microsoft.com/en-us/azure/developer/jenkins/deploy-to-linux-vm-using-azure-devops-services
D. Create a PAT in your Azure DevOps account. Unique identifier and a secret that you can use to authenticate Jenkins with Azure Devops. Serves as the credentials for Jenkins to access your Azure Repos securely. B. Add the Team Foundation Server (TFS) plug-in to Jenkins. Enables Jenkins to communicate with Azure DevOps and allows it to use the created PAT for authentication. C. Add the PAT to your Jenkins account. You provide the PAT during the plug-in configuration to allow Jenkins to authenticate itself and access Azure Repos securely.