-
Notifications
You must be signed in to change notification settings - Fork 98
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* docs: update webhook manuals * docs: update webhook manuals in v0.20 --------- Co-authored-by: Startrekzky <[email protected]>
- Loading branch information
1 parent
631bc25
commit fb2bd65
Showing
7 changed files
with
37 additions
and
21 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,42 +1,49 @@ | ||
--- | ||
title: "Webhooks" | ||
sidebar_position: 25 | ||
description: Config UI instruction for Webhook | ||
description: Config UI instructions for Webhook | ||
--- | ||
|
||
Visit config-ui: `http://{localhost}:4000`. | ||
|
||
### Step 1 - Add a new incoming webhook | ||
|
||
Go to the 'Data Connections' page. Create a webhook. | ||
Go to the 'Connections' page. Create a webhook with a unique name. | ||
|
||
![webhook-add-data-connections](/img/ConfigUI/webhook-add-data-connections.png) | ||
![webhook-add-data-connections](images/webhook-add.png) | ||
|
||
We recommend that you give your webhook connection a unique name so that you can identify and manage where you have used it later. | ||
|
||
### Step 2 - Create webhooks connection | ||
|
||
Click on Generate POST URL, and you will find three webhook URLs. | ||
|
||
![webhook-connection1](images/webhook-connection1.png) | ||
|
||
Revoke and generate a new key. Copy the ones that suit your usage into your CI/CD or issue-tracking systems. You can always come back to the webhook page to copy the URLs later on. | ||
![webhook-connection2](images/webhook-connection2.png) | ||
Copy the ones that suit your usage into your CI/CD or issue-tracking systems. You can always come back to the webhook page to copy the URLs later on. | ||
|
||
A non-expired API key is auto-generated for the authentication of the webhook. This API key only shows in the payload when you create the webhook. However, you can always revoke and generate a new token when you view the webhook details. | ||
|
||
See the [full payload schema](../Plugins/webhook.md) of webhooks. | ||
|
||
### Step 3 - Use webhook in a project | ||
|
||
Create a Project first, choose Incoming Webhooks, then you can `Add a Webhook` or `Select Existing Webhooks`. | ||
If you want to use webhook data to measure [DORA metrics](../DORA.md), you have to associate it with a DevLake project. | ||
|
||
- Go to the 'Incoming Webhooks' tab on a project's page. | ||
- Add webhook by selecting the existing webhook. | ||
- Go to the project's blueprint page and click 'Collect Data'. This will trigger the DORA plugin to measure DORA metrics with the data collected by the [data connections and webhooks associated with this project](HowToOrganizeDevlakeProjects.md#2-why-is-it-important-to-organize-projects). | ||
|
||
![project-webhook-use](/img/ConfigUI/project-webhook-use.png) | ||
|
||
#### Put webhook on the internet | ||
|
||
For the new webhook to work, it needs to be accessible from the DevOps tools from which you would like to push data to DevLake. If DevLake is deployed in your private network and your DevOps tool (e.g. CircleCI) is a cloud service that lives outside of your private network, then you need to make DevLake's webhook accessible to the outside cloud service. | ||
|
||
There're many tools for this: | ||
There are many tools for this: | ||
|
||
- For testing and quick setup, [ngrok](https://ngrok.com/) is a useful utility that provides a publicly accessible web URL to any locally hosted application. You can put DevLake's webhook on the internet within 5 mins by following ngrok's [Getting Started](https://ngrok.com/docs/getting-started) guide. Note that, when posting to webhook, you may need to replace the `localhost` part in the webhook URL with the forwarding URL that ngrok provides. | ||
- If you prefer DIY, please checkout open-source reverse proxies like [fatedier/frp](https://github.com/fatedier/frp) or go for the classic [nginx](https://www.nginx.com/). | ||
- If you prefer DIY, please check out open-source reverse proxies like [fatedier/frp](https://github.com/fatedier/frp) or go for the classic [nginx](https://www.nginx.com/). | ||
|
||
## Troubleshooting | ||
|
||
If you run into any problem, please check the [Troubleshooting](/Troubleshooting/Configuration.md) or [create an issue](https://github.com/apache/incubator-devlake/issues) | ||
If you run into any problems, please check the [Troubleshooting](/Troubleshooting/Configuration.md) or [create an issue](https://github.com/apache/incubator-devlake/issues). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+87.9 KB
versioned_docs/version-v0.20/Configuration/images/webhook-connection1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,40 +1,49 @@ | ||
--- | ||
title: "Incoming Webhook" | ||
title: "Webhooks" | ||
sidebar_position: 8 | ||
description: Config UI instruction for Webhook | ||
description: Config UI instructions for Webhook | ||
--- | ||
|
||
Visit config-ui: `http://{localhost}:4000`. | ||
|
||
### Step 1 - Add a new incoming webhook | ||
|
||
Go to the 'Data Connections' page. Create a webhook. | ||
Go to the 'Connections' page. Create a webhook with a unique name. | ||
|
||
![webhook-add-data-connections](/img/ConfigUI/webhook-add-data-connections.png) | ||
![webhook-add-data-connections](images/webhook-add.png) | ||
|
||
We recommend that you give your webhook connection a unique name so that you can identify and manage where you have used it later. | ||
|
||
### Step 2 - Create webhooks connection | ||
|
||
Click on Generate POST URL, and you will find three webhook URLs. Copy the ones that suit your usage into your CI or issue-tracking systems. You can always come back to the webhook page to copy the URLs later on. | ||
Click on Generate POST URL, and you will find three webhook URLs. | ||
|
||
![webhook-connection](/img/ConfigUI/webhook-connection.png) | ||
![webhook-connection1](images/webhook-connection1.png) | ||
|
||
Copy the ones that suit your usage into your CI/CD or issue-tracking systems. You can always come back to the webhook page to copy the URLs later on. | ||
|
||
A non-expired API key is auto-generated for the authentication of the webhook. This API key only shows in the payload when you create the webhook. However, you can always revoke and generate a new token when you view the webhook details. | ||
|
||
See the [full payload schema](../Plugins/webhook.md) of webhooks. | ||
|
||
### Step 3 - Use webhook in a project | ||
|
||
Create a Project first, choose Incoming Webhooks, then you can `Add a Webhook` or `Select Existing Webhooks`. | ||
If you want to use the webhook data to measure [DORA metrics](../DORA.md), you have to associate it with a DevLake project. | ||
|
||
- Go to the 'Incoming Webhooks' tab on a project's page. | ||
- Add webhook by selecting the existing webhook. | ||
- Go to the project's blueprint page and click 'Collect Data'. This will trigger the DORA plugin to measure DORA metrics with the data collected by the [data connections and webhooks associated with this project](../GettingStarted/HowToOrganizeDevlakeProjects.md#2-why-is-it-important-to-organize-projects). | ||
|
||
![project-webhook-use](/img/ConfigUI/project-webhook-use.png) | ||
|
||
#### Put webhook on the internet | ||
|
||
For the new webhook to work, it needs to be accessible from the DevOps tools from which you would like to push data to DevLake. If DevLake is deployed in your private network and your DevOps tool (e.g. CircleCI) is a cloud service that lives outside of your private network, then you need to make DevLake's webhook accessible to the outside cloud service. | ||
|
||
There're many tools for this: | ||
There are many tools for this: | ||
|
||
- For testing and quick setup, [ngrok](https://ngrok.com/) is a useful utility that provides a publicly accessible web URL to any locally hosted application. You can put DevLake's webhook on the internet within 5 mins by following ngrok's [Getting Started](https://ngrok.com/docs/getting-started) guide. Note that, when posting to webhook, you may need to replace the `localhost` part in the webhook URL with the forwarding URL that ngrok provides. | ||
- If you prefer DIY, please checkout open-source reverse proxies like [fatedier/frp](https://github.com/fatedier/frp) or go for the classic [nginx](https://www.nginx.com/). | ||
- If you prefer DIY, please check out open-source reverse proxies like [fatedier/frp](https://github.com/fatedier/frp) or go for the classic [nginx](https://www.nginx.com/). | ||
|
||
## Troubleshooting | ||
|
||
If you run into any problem, please check the [Troubleshooting](/Troubleshooting/Configuration.md) or [create an issue](https://github.com/apache/incubator-devlake/issues) | ||
If you run into any problems, please check the [Troubleshooting](/Troubleshooting/Configuration.md) or [create an issue](https://github.com/apache/incubator-devlake/issues). |