Get started
Sign in

Azure DevOps

Receive Azure DevOps work item and pull request events in Plural

An Azure DevOps webhook delivers work item, pull request, and PR comment events from Azure DevOps into Plural. After you configure the source once, you can attach it to one or more workbench triggers to start jobs based on work item or code review changes.

This guide uses the Plural Console UI and Azure DevOps service hooks. For general webhook behavior and trigger configuration, see Webhooks.

Prerequisites

Before you begin, make sure you have:

  • An Azure DevOps organization and project with work items or pull requests you want to monitor.
  • Permission in your Azure DevOps project to create service hook subscriptions. This typically requires project administrator or collection administrator permissions.
  • Permission in Plural Console to create a webhook source and configure workbench triggers.
  • An HTTPS-accessible Plural deployment. Azure DevOps webhooks require HTTPS and must reach your endpoint over the public internet (or your network must allow Azure DevOps inbound IP ranges if you use restrictions).

Capabilities

Azure DevOps webhooks deliver service hook events:

  • Work item created — a new work item (bug, task, user story, or custom type) is created.
  • Work item updated — work item fields such as title, description, state, assignee, or custom fields are modified.
  • Work item commented — a comment is added to a work item.
  • Work item deleted — a work item is removed.
  • Pull request created, updated, or merged — a pull request lifecycle event occurs.
  • Pull request comment — a comment is added to a pull request.

Plural accepts Azure DevOps service hook payloads whose eventType begins with workitem. (for example workitem.created, workitem.updated) or that contain pullRequest data in the resource field. Work items include detailed field information (title, description, repro steps, acceptance criteria, and custom fields). Pull requests include title, description, and status.

Inbound events are stored as issues in Plural and do not start a job until a workbench trigger matches the payload content. See Webhook triggers for binding events to workbenches.

Edit on Github