You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: configuration.md
+4-8Lines changed: 4 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -41,19 +41,15 @@ Configure a Github project with a webhook with a format like this: https://<rece
41
41
42
42
You can test other events, but just validating that an issue.created event is generated in Kafka is enough to smoke test the receiver is set up properly.
43
43
44
-
#### Debugging
45
-
You can re-run and debug the responses to webhook requests on Github, in the configuration for the webhook. This can be useful if things aren't coming through properly in the receiver.
46
-
47
-
## Github Verification
44
+
## Gitlab Verification
48
45
49
46
#### Webhook configuration
50
47
51
48
Configure a Gitlab project with a webhook with a format like this: https://<receiverURL>:<receiverport>/webhooks/gitlab
52
49
53
50
#### Smoke test
54
-
- Create an issue in the repo, you can see the logs in `receiver`, the `issue.created` event is generated.
55
51
56
-
You can test other events, but just validating that an issue.created event is generated in Kafka is enough to smoke test the receiver is set up properly.
52
+
See above - the steps are the same for Github and Gitlab
57
53
58
-
####Debugging
59
-
You can re-run and debug the responses to webhook requests on Gitlab, in the configuration for the webhook. This can be useful if things aren't coming through properly in the receiver.
54
+
## Debugging
55
+
You can re-run and debug the responses to webhook requests on Github and Gitlab, in the configuration for the webhook. This can be useful if things aren't coming through properly in the receiver.
0 commit comments