Integrations / Jenkins

Jenkins notifications in Microsoft Teams

Jenkins job results in Teams via the standard Notification Plugin — no scripting required. Per My Last Webhook normalizes Jenkins events into rich Adaptive Cards and posts them to a Teams channel, a person's DM, or a webhook — the successor to Office 365 Connectors.

How it works

  1. Jenkins POSTs a webhook to your private ingest URL when a build runs.
  2. We normalize it — the same card format as every other platform.
  3. The card lands in your chosen Teams destination, with routing and noise controls applied.

Set up in minutes

Create a subscription in the app (platform: Jenkins), copy its ingest URL, then:

1

Install the Notification Plugin (Manage Plugins).

2

Job → Configure → Job Notifications → Add Endpoint.

3

Format JSON · Protocol HTTP · Event Job Finalized.

4

URL: your ingest URL. Save.

See it instantly

Don't want to wait for a build? Hit Test on the subscription — a card lands immediately. Full steps in the platform reference.

What lands in Teams

Teams · #ci
🔴 build-service · failure
Jenkins · main · alice · 3m 20s

Built for teams, not just alerts

Routing PRO

Prod failures to #prod-alerts, the rest to #ci.

Incident mode PRO

Collapse a flapping pipeline into one updating card.

On-call DMs PRO

DM the owner the moment their Jenkins build breaks.

Status filters

Only care about failures? Filter to just those — free.

Part of Per My Last Webhook — all 17 integrations into one Teams app.

▣ StartPER MY LAST WEBHOOKC:\INTEGRATIONS\JENKINSStatus: 200 OK