mirror of
https://github.com/zulip/zulip.git
synced 2025-11-08 16:01:58 +00:00
7e7e6b7ba9
Using an if block when {!event-filtering-additional-feature.md!}
is used implied that we plan to have this in all webhook doc .md
files.
But, it actually makes sense to only use this macro when the
webhook integration actually supports event filtering.
35 lines
932 B
Markdown
35 lines
932 B
Markdown
# Zulip CircleCI integration
|
|
|
|
Zulip supports integration with CircleCI and can notify you of your
|
|
job and workflow statuses. This integration currently supports using
|
|
CircleCI with GitHub, BitBucket and GitLab.
|
|
|
|
{start_tabs}
|
|
|
|
1. {!create-channel.md!}
|
|
|
|
1. {!create-an-incoming-webhook.md!}
|
|
|
|
1. {!generate-webhook-url-basic.md!}
|
|
|
|
1. Go to **Project Settings** in your project on CircleCI. Select
|
|
**Webhooks** from the list on the left, and click **Add Webhook**.
|
|
|
|
1. In the form that opens, give your webhook a name and set the
|
|
**Receiver URL** field to the URL generated above. Choose the
|
|
[events](#filtering-incoming-events) you'd like to be notified about,
|
|
and click **Add Webhook**.
|
|
|
|
{end_tabs}
|
|
|
|
{!congrats.md!}
|
|
|
|
|
|
|
|
|
|
{!event-filtering-additional-feature.md!}
|
|
|
|
### Related documentation
|
|
|
|
{!webhooks-url-specification.md!}
|