Merge pull request #493 from chwetion/dockerhub-and-jfrog-trigger-docs

Docs: update trigger how to docs
This commit is contained in:
barnettZQG 2022-02-07 09:54:12 +08:00 committed by GitHub
commit fa55e3f35b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
21 changed files with 108 additions and 3 deletions

View File

@ -94,4 +94,39 @@ After configuring the trigger, we can see the new deploy revisions when a new im
![alt](../../../resources/acr-trigger-acrrecord.png)
![alt](../../../resources/acr-trigger-revisions.png)
![alt](../../../resources/acr-trigger-revisions.png)
## DockerHub Trigger
DockerHub Trigger can be integrated with DockerHub.
We can start with creating a new DockerHub trigger. The Payload Type is DockerHub, and the Execution Workflow is the workflow you want to deploy in the trigger.
![alt](../../../resources/dockerhub-trigger-newtrigger.png)
After creating the trigger, we can setup this trigger in DockerHub:
![alt](../../../resources/dockerhub-trigger.png)
After configuring the trigger, we can see the new deploy revisions when a new image is pushed to the registry.
![alt](../../../resources/dockerhub-trigger-dockerhubrecord.png)
![alt](../../../resources/dockerhub-trigger-revisions.png)
## JFrog Trigger
jFrog Trigger can be integrated with JFrog Artifactory.
We can start with creating a new jFrog trigger. The Payload Type is jFrog, and the Execution Workflow is the workflow you want to deploy in the trigger.
![alt](../../../resources/jfrog-trigger-newtrigger.png)
After creating the trigger, we can setup this trigger in jFrog:
![alt](../../../resources/jfrog-trigger.png)
After configuring the trigger, we can see the new deploy revisions when a new image is pushed to the registry.
Note: jFrog webhook callback has no jFrog address, KubeVela will recognize the request header `X-jFrogURL` as jFrog address and use it in application `image` field.

Binary file not shown.

After

Width:  |  Height:  |  Size: 115 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 156 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 231 KiB

View File

@ -94,4 +94,39 @@ ACR 触发器可以对接 ACR 镜像仓库。
![alt](../../../resources/acr-trigger-acrrecord.png)
![alt](../../../resources/acr-trigger-revisions.png)
![alt](../../../resources/acr-trigger-revisions.png)
## DockerHub 触发器
DockerHub 触发器可以对接 DockerHub 仓库。
首先来创建一个 DockerHub 触发器Payload Type 选择 dockerhubExecution Workflow 选择触发器要触发的工作流:
![alt](../../../resources/dockerhub-trigger-newtrigger.png)
新建完毕后,在 DockerHub 中配置该触发器:
![alt](../../../resources/dockerhub-trigger.png)
配置完成后,当 DockerHub 中被推送了镜像时VelaUX 中会收到对应的触发请求,从而完成自动部署。
![alt](../../../resources/dockerhub-trigger-dockerhubrecord.png)
![alt](../../../resources/dockerhub-trigger-revisions.png)
## JFrog 触发器
JFrog 触发器可以对接 JFrog Artifactory。
首先来创建一个 JFrog 触发器Payload Type 选择 jfrog Workflow 选择触发器要触发的工作流:
![alt](../../../resources/jfrog-trigger-newtrigger.png)
新建完毕后,在 JFrog 中配置该触发器:
![alt](../../../resources/jfrog-trigger.png)
配置完成后,当 JFrog 中被推送了镜像时VelaUX 中会收到对应的触发请求,从而完成自动部署。
注意:由于 jFrog 的回调请求中不包含 jFrog 本身的地址KubeVela 将识别在 jFrog Webhook 中配置的 `X-jFrogURL` 地址,将其写入到应用的 `image` 字段中。

Binary file not shown.

After

Width:  |  Height:  |  Size: 115 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 156 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 231 KiB

View File

@ -94,4 +94,39 @@ ACR 触发器可以对接 ACR 镜像仓库。
![alt](../../../resources/acr-trigger-acrrecord.png)
![alt](../../../resources/acr-trigger-revisions.png)
![alt](../../../resources/acr-trigger-revisions.png)
## DockerHub 触发器
DockerHub 触发器可以对接 DockerHub 仓库。
首先来创建一个 DockerHub 触发器Payload Type 选择 dockerhubExecution Workflow 选择触发器要触发的工作流:
![alt](../../../resources/dockerhub-trigger-newtrigger.png)
新建完毕后,在 DockerHub 中配置该触发器:
![alt](../../../resources/dockerhub-trigger.png)
配置完成后,当 DockerHub 中被推送了镜像时VelaUX 中会收到对应的触发请求,从而完成自动部署。
![alt](../../../resources/dockerhub-trigger-dockerhubrecord.png)
![alt](../../../resources/dockerhub-trigger-revisions.png)
## JFrog 触发器
JFrog 触发器可以对接 JFrog Artifactory。
首先来创建一个 JFrog 触发器Payload Type 选择 jfrog Workflow 选择触发器要触发的工作流:
![alt](../../../resources/jfrog-trigger-newtrigger.png)
新建完毕后,在 JFrog 中配置该触发器:
![alt](../../../resources/jfrog-trigger.png)
配置完成后,当 JFrog 中被推送了镜像时VelaUX 中会收到对应的触发请求,从而完成自动部署。
注意:由于 jFrog 的回调请求中不包含 jFrog 本身的地址KubeVela 将识别在 jFrog Webhook 中配置的 `X-jFrogURL` 地址,将其写入到应用的 `image` 字段中。

Binary file not shown.

After

Width:  |  Height:  |  Size: 115 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 156 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 69 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 231 KiB