Merge pull request #493 from chwetion/dockerhub-and-jfrog-trigger-docs
Docs: update trigger how to docs
|
@ -94,4 +94,39 @@ After configuring the trigger, we can see the new deploy revisions when a new im
|
|||
|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
## 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.
|
||||
|
||||

|
||||
|
||||
After creating the trigger, we can setup this trigger in DockerHub:
|
||||
|
||||

|
||||
|
||||
After configuring the trigger, we can see the new deploy revisions when a new image is pushed to the registry.
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
## 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.
|
||||
|
||||

|
||||
|
||||
|
||||
After creating the trigger, we can setup this trigger in jFrog:
|
||||
|
||||

|
||||
|
||||
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.
|
After Width: | Height: | Size: 115 KiB |
After Width: | Height: | Size: 70 KiB |
After Width: | Height: | Size: 138 KiB |
After Width: | Height: | Size: 156 KiB |
After Width: | Height: | Size: 69 KiB |
After Width: | Height: | Size: 231 KiB |
|
@ -94,4 +94,39 @@ ACR 触发器可以对接 ACR 镜像仓库。
|
|||
|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
## DockerHub 触发器
|
||||
|
||||
DockerHub 触发器可以对接 DockerHub 仓库。
|
||||
|
||||
首先来创建一个 DockerHub 触发器,Payload Type 选择 dockerhub,Execution Workflow 选择触发器要触发的工作流:
|
||||
|
||||

|
||||
|
||||
新建完毕后,在 DockerHub 中配置该触发器:
|
||||
|
||||

|
||||
|
||||
配置完成后,当 DockerHub 中被推送了镜像时,VelaUX 中会收到对应的触发请求,从而完成自动部署。
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
## JFrog 触发器
|
||||
|
||||
JFrog 触发器可以对接 JFrog Artifactory。
|
||||
|
||||
首先来创建一个 JFrog 触发器,Payload Type 选择 jfrog, Workflow 选择触发器要触发的工作流:
|
||||
|
||||

|
||||
|
||||
|
||||
新建完毕后,在 JFrog 中配置该触发器:
|
||||
|
||||

|
||||
|
||||
配置完成后,当 JFrog 中被推送了镜像时,VelaUX 中会收到对应的触发请求,从而完成自动部署。
|
||||
|
||||
注意:由于 jFrog 的回调请求中不包含 jFrog 本身的地址,KubeVela 将识别在 jFrog Webhook 中配置的 `X-jFrogURL` 地址,将其写入到应用的 `image` 字段中。
|
After Width: | Height: | Size: 115 KiB |
After Width: | Height: | Size: 70 KiB |
After Width: | Height: | Size: 138 KiB |
After Width: | Height: | Size: 156 KiB |
After Width: | Height: | Size: 69 KiB |
After Width: | Height: | Size: 231 KiB |
|
@ -94,4 +94,39 @@ ACR 触发器可以对接 ACR 镜像仓库。
|
|||
|
||||

|
||||
|
||||

|
||||

|
||||
|
||||
## DockerHub 触发器
|
||||
|
||||
DockerHub 触发器可以对接 DockerHub 仓库。
|
||||
|
||||
首先来创建一个 DockerHub 触发器,Payload Type 选择 dockerhub,Execution Workflow 选择触发器要触发的工作流:
|
||||
|
||||

|
||||
|
||||
新建完毕后,在 DockerHub 中配置该触发器:
|
||||
|
||||

|
||||
|
||||
配置完成后,当 DockerHub 中被推送了镜像时,VelaUX 中会收到对应的触发请求,从而完成自动部署。
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
## JFrog 触发器
|
||||
|
||||
JFrog 触发器可以对接 JFrog Artifactory。
|
||||
|
||||
首先来创建一个 JFrog 触发器,Payload Type 选择 jfrog, Workflow 选择触发器要触发的工作流:
|
||||
|
||||

|
||||
|
||||
|
||||
新建完毕后,在 JFrog 中配置该触发器:
|
||||
|
||||

|
||||
|
||||
配置完成后,当 JFrog 中被推送了镜像时,VelaUX 中会收到对应的触发请求,从而完成自动部署。
|
||||
|
||||
注意:由于 jFrog 的回调请求中不包含 jFrog 本身的地址,KubeVela 将识别在 jFrog Webhook 中配置的 `X-jFrogURL` 地址,将其写入到应用的 `image` 字段中。
|
After Width: | Height: | Size: 115 KiB |
After Width: | Height: | Size: 70 KiB |
After Width: | Height: | Size: 138 KiB |
After Width: | Height: | Size: 156 KiB |
After Width: | Height: | Size: 69 KiB |
After Width: | Height: | Size: 231 KiB |