HackerOne Code Review (Azure DevOps)
  • Introduction
  • Create Account & Organization
  • Installing the PullRequest Proxy
  • Configuring your Proxy to Connect to the Code Review Server
  • Configure Posting User
    • Configure Azure DevOps Posting User
  • Configuring SSL
  • Start the PullRequest Proxy
  • Verify Data on PullRequest
  • Configure Webhooks
    • Configure Azure DevOps Webhooks
  • Assigning Pull Requests with Posting User
  • Upgrading the PullRequest Proxy
Powered by GitBook
On this page
  • Configure Webhooks
  • Applying Webhooks
  • Webhook Security
  1. Configure Webhooks

Configure Azure DevOps Webhooks

After the Azure DevOps posting user has been created and the repositories are populating in PullRequest code review application successfully, the Azure DevOps webhooks can be configured.

PreviousConfigure WebhooksNextAssigning Pull Requests with Posting User

Last updated 1 year ago

Configure Webhooks

Azure DevOps allows webhooks to be configured on the Azure DevOps project level.

Applying Webhooks

From your Azure DevOps project page, click Project settings, then select Service hooks from the sidebar. We're actually going to create three webhooks here via the same method:

  • Code pushed

  • Pull request created

  • Pull request updated

From here, click the green "+" button to create a webhook. This will open up an overlay. From here, click Web Hooks from the sidebar, then click Next.

On this next page, pick the event to configure a webhook for. We'll be doing this for each of the events above. It's recommended that you choose [Any] for all of the options as this ensures you don't have to re-configure these hooks every time you add a repository.

On this next page, we'll put the webhook endpoint to configure. This will be the same for all webhooks. Ensure the hostname or IP address given can be used to access the proxy server:

You can use the Test button to test that this webhook endpoint can be reached. When finished, click Finish.

Complete these steps for all necessary webhooks.

Webhook Security

This step is optional, but recommended. If you'd like added security for outgoing webhooks, you can specify a Basic authentication username and a Basic authentication password when entering the webhook URL.

  • You will need the same webhook secret for all of your organizations/repositories if you add one.

  • The username and password must match the PROVIDER_WEBHOOK_SECRET field when you configured the proxy.