Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
89097ed6
Commit
89097ed6
authored
Jun 23, 2017
by
Marcia Ramos
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add overview and use-cases to webhooks doc (replaces !632)
parent
f9b8c33d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
28 additions
and
0 deletions
+28
-0
doc/user/project/integrations/webhooks.md
doc/user/project/integrations/webhooks.md
+28
-0
No files found.
doc/user/project/integrations/webhooks.md
View file @
89097ed6
...
@@ -6,6 +6,34 @@ Starting from GitLab 8.5:
...
@@ -6,6 +6,34 @@ Starting from GitLab 8.5:
-
the
`project.ssh_url`
key is deprecated in favor of the
`project.git_ssh_url`
key
-
the
`project.ssh_url`
key is deprecated in favor of the
`project.git_ssh_url`
key
-
the
`project.http_url`
key is deprecated in favor of the
`project.git_http_url`
key
-
the
`project.http_url`
key is deprecated in favor of the
`project.git_http_url`
key
## Overview
[
Webhooks
](
https://en.wikipedia.org/wiki/Webhook
)
are "_user-defined HTTP
callbacks_". They are usually triggered by some
event, such as pushing code to a repository or a comment being posted to a blog.
When that event occurs, the source app makes an HTTP request to the URI
configured for the webhook. The action taken may be anything.
Common uses are to trigger builds with continuous integration systems or to
notify bug tracking systems.
Webhooks are available
**per project**
for GitLab Community Edition,
and
**per project and per group**
for
**GitLab Enterprise Edition**
.
In most cases, you'll need to setup your own
[
webhook receiver
](
#example-webhook-receiver
)
to receive infomation from GitLab, and send it to another app, according to your needs.
We already have a
[
built-in receiver
](
http://docs.gitlab.com/ce/project_services/slack.html
)
for sending
[
Slack
](
https://api.slack.com/incoming-webhooks
)
notifications _per project_.
## Use-cases
-
You can setup a webhook in GitLab to send a notification to
[
Slack
](
https://api.slack.com/incoming-webhooks
)
every time a build fails, for example
-
You can
[
integrate with Twilio to be notified via SMS
](
https://www.datadoghq.com/blog/send-alerts-sms-customizable-webhooks-twilio/
)
every time an issue is created for a specific project or group within GitLab
-
You can use them to
[
automatically assign labels to merge requests
](
https://about.gitlab.com/2016/08/19/applying-gitlab-labels-automatically/
)
.
## Description
Project webhooks allow you to trigger a URL if for example new code is pushed or
Project webhooks allow you to trigger a URL if for example new code is pushed or
a new issue is created. You can configure webhooks to listen for specific events
a new issue is created. You can configure webhooks to listen for specific events
like pushes, issues or merge requests. GitLab will send a POST request with data
like pushes, issues or merge requests. GitLab will send a POST request with data
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment