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
5235579d
Commit
5235579d
authored
Jan 07, 2021
by
Mike Jang
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'eread/improve-webhooks-topic' into 'master'
Improve webhooks topic See merge request gitlab-org/gitlab!50926
parents
1e5bf837
d73d2221
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
25 deletions
+6
-25
doc/user/project/integrations/img/webhooks_ssl.png
doc/user/project/integrations/img/webhooks_ssl.png
+0
-0
doc/user/project/integrations/webhooks.md
doc/user/project/integrations/webhooks.md
+6
-25
No files found.
doc/user/project/integrations/img/webhooks_ssl.png
deleted
100644 → 0
View file @
1e5bf837
57.2 KB
doc/user/project/integrations/webhooks.md
View file @
5235579d
...
...
@@ -28,32 +28,15 @@ notify bug tracking systems.
Webhooks can be used to update an external issue tracker, trigger CI jobs,
update a backup mirror, or even deploy to your production server.
They are available
**per project**
for GitLab Community Edition,
and
**per project and per group**
for
**GitLab Enterprise Edition**
.
Navigate to the webhooks page at your project's
**Settings > Webhooks**
.
Webhooks are available:
-
Per project, at a project's
**Settings > Webhooks**
menu.
**(CORE)**
-
Additionally per group, at a group's
**Settings > Webhooks**
menu.
**(PREMIUM)**
NOTE:
On GitLab.com, the
[
maximum number of webhooks and their size
](
../../../user/gitlab_com/index.md#webhooks
)
per project, and per group, is limited.
## Version history
Starting from GitLab 8.5:
-
the
`repository`
key is deprecated in favor of the
`project`
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
Starting from GitLab 11.1, the logs of webhooks are automatically removed after
one month.
Starting from GitLab 11.2:
-
The
`description`
field for issues, merge requests, comments, and wiki pages
is rewritten so that simple Markdown image references (like
`![](/uploads/...)`
) have their target URL changed to an absolute URL. See
[
image URL rewriting
](
#image-url-rewriting
)
for more details.
## Possible uses for webhooks
-
You can set up a webhook in GitLab to send a notification to
...
...
@@ -91,8 +74,6 @@ be self-signed.
You can turn this off in the webhook settings in your GitLab projects.
![
SSL Verification
](
img/webhooks_ssl.png
)
## Branch filtering
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/20338) in GitLab 11.3.
...
...
@@ -1362,7 +1343,7 @@ X-Gitlab-Event: Deployment Hook
Note that
`deployable_id`
is the ID of the CI job.
###
M
ember events **(PREMIUM)**
###
Group m
ember events **(PREMIUM)**
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/260347) in GitLab 13.7.
...
...
@@ -1554,7 +1535,7 @@ Markdown features, like link labels.
## Testing webhooks
You can trigger the webhook manually. Sample data from the project is used.
> For example:
for triggering `Push Events` your project should have at least one commit.
For example,
for triggering
`Push Events`
your project should have at least one commit.
![
Webhook testing
](
img/webhook_testing.png
)
...
...
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