Triggers

• Custom, refer to guide for a real world use case
• ACR
• , refer to Harbor Integration guide for a real world use case
• JFrog

A default trigger will be automatically generated after an application created. You can also delete it and create a new one.

KubeVela triggers can integrate with any CI tool like Gitlab CI, Jenkins Pipeline or image registry like Harbor or ACR.

Custom Trigger

Custom triggers will provide a webhook URL, which you can use to integrate with your CI tool using the specified request body.

The default trigger is a custom trigger, click to get more info of this trigger:

Webhook URL is the address of this trigger, you can see request body in Curl Command example:

upgrade is the key of the object that need to be patched, <application-name> is the name of application. image is the field that need to be patched. You can also add more fields in .

In codeInfo, you can add some code infos of this deployment like commit id, branch or user.

Below is an example of using Custom Trigger in Gitlab CI, we use env in this example:

  stage: request
  before_script:
  script:
    - |

After CI have executed this step, we can see that application is deployed successfully in VelaUX. We can also see some relative code infos of this deployment.

You can refer to guide for a real use case about custom trigger.

Harbor Trigger can be integrated with Harbor image registry.

You can refer to guide for the end to end tutorial.

ACR Trigger

ACR Trigger can be integrated with ACR image registry.

We can start with creating a new ACR trigger. The Payload Type is ACR, and the Execution Workflow is the workflow you want to deploy in the trigger.

After creating the trigger, we can setup this trigger in ACR:

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

DockerHub Trigger can be integrated with DockerHub.

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.