From e6c26dfa527417cd6fe6a62662d76b4182ab227d Mon Sep 17 00:00:00 2001 From: Ohad Zamir <130290917+odzmrfrog@users.noreply.github.com> Date: Thu, 2 Jan 2025 10:34:46 +0200 Subject: [PATCH] Update setup-frogbot-using-azure-pipelines.md --- .../frogbot/setup-frogbot-using-azure-pipelines.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/jfrog-applications/frogbot/setup-frogbot-using-azure-pipelines.md b/jfrog-applications/frogbot/setup-frogbot-using-azure-pipelines.md index 3761a411..26fd4ac1 100644 --- a/jfrog-applications/frogbot/setup-frogbot-using-azure-pipelines.md +++ b/jfrog-applications/frogbot/setup-frogbot-using-azure-pipelines.md @@ -349,10 +349,11 @@ jobs: _**NOTE:**_ To set up a pull request trigger in Azure Repos, you need to add a branch policy via 'Branch Policies'. * Go to the "Branches" section: -* For each of the branches against which you want Frogbot to scan pull requests, click on the three dots and select "Branch policies": -* Add new build policy: +* For each of the target branches against which you want Frogbot to scan pull requests, click on the three dots and select "Branch Policies": +* Under Policies > Build Validation add a new Build Policy: * Fill the following build policy parameters and Save: - + - Under Build Pipeline Choose the Pipline. + - Make sure the policy is enabled, and the trigger is set to Automatic. 8. For the pipeline you created, save the JFrog connection details as variables with the following names - JF\_URL, JF\_USER, and JF\_PASSWORD.