Overview
This article introduces the basic concepts of Zadig workflows. Zadig workflows support flexible orchestration of workflow processes, custom execution steps, and also possess capabilities such as configuration changes, data changes, and grayscale releases.

# Basic Concepts
Workflows consist of stages and tasks:
- Stage: Logically group the tasks of the workflow, such as the build stage, the deployment stage... Multiple stages run in series, and one stage can include multiple tasks.
- Task: An independent and complete operation, such as building, deploying, testing, custom tasks... Multiple tasks can be executed serially or concurrently. Tasks are divided into two types:
- Custom tasks: Interact with third-party systems through the development of custom tasks. For specific development methods, see Workflow tasks
- Official tasks: Zadig officially provides tasks that can meet complex needs for building, deploying, testing, and releasing. The specific task types are as follows:
| Task Type | Task Name | Description | Configuration |
|---|---|---|---|
| Build | Build | You can directly reference the configuration in the "Project"-"Build" module | Check |
| Deploy | Container Service Deployment | Update service images, variables, and service configurations in Zadig environments | Check |
| Host Service Deployment | Update the host service version in the Zadig environment | Check | |
| Kubernetes Deployment | Update container images in Kubernetes | Check | |
| Update K8s YAML Task | Use native Kubernetes Patch capabilities to update YAML | Check | |
| Test | Test | You can directly reference the test configuration in the "Project"-"Test" module | Check |
| Code scanning | You can directly reference the configuration in the "Project"-"Code Scan" module | Check | |
| Process Control | Manual Approval | Follow-up operations can only be performed after approval | Check |
| Release Strategies | Helm Chart Deployment | Directly deploy Charts from the Helm repository to the environment | Check |
| MSE Grayscale Release | Create full-link grayscale publishing resources based on MSE | Check | |
| Offline MSE Grayscale Service | Delete MSE Specified Grayscale Tag-Related Resources from the Environment | Check | |
| Deploy Blue and Green Environments | Deploy blue and green environments based on the configuration in the "Service" module | Check | |
| Blue-Green Release | Combined with the pre-installed "Deploy Blue and Green Environments", perform blue and green releases | Check | |
| Canary Deployment | Deploy the Canary based on Kubernetes native capabilities | Check | |
| Canary Release | Combined with the pre-installed "Canary Deployment" task, perform Canary releases | Check | |
| Grayscale Release | Perform grayscale releases based on Kubernetes native capabilities | Check | |
| Grayscale Rollback | Perform rollback tasks based on Kubernetes native capabilities, rolling back to the state before grayscale | Check | |
| Istio Release | Perform the release process based on Istio | Check | |
| Istio Rollback | Perform rollback tasks based on Istio, rolling back to the state before the Istio release | Check | |
| Update Istio Grayscale Policy | Update the configuration of Istio grayscale policy in the environment | Check | |
| Project Collaboration | Feishu Work Item Status Change | Modify the status of the specified Feishu project work item | Check |
| JIRA Issue Status Change | Modify the status of the specified JIRA issue | Check | |
| PingCode Work Item Status Change | Modify the status of the specified PingCode project work item | Check | |
| Tapd Work Item Status Change | Modify the status of the specified Tapd project work item | Check | |
| Configuration changes | Nacos Configuration Change | Update the specified Nacos configuration | Check |
| Apollo Configuration Change | Update and publish the specified Apollo configuration | Check | |
| Data changes | SQL Data Change | Perform data changes for the specified database | Check |
| DMS Data Change Work Order | Create and track DMS data change work orders | Check | |
| Gateway Changes | APISIX Gateway Changes | Update the configuration of the specified APISIX gateway | Check |
| Service Monitoring | Grafana Monitoring | Use Grafana to monitor the health of your services | Check |
| CI/CD | Execute Jenkins Job | Execute multiple Jenkins jobs simultaneously and obtain corresponding logs | Check |
| Execute Blue Whale Job | Trigger the execution plan of the Blue Whale Operation Platform | Check | |
| Other Requirements | General Task | Support functions such as pulling code, executing shell scripts, file storage, etc | Check |
| Image Distribution | Push the retagged image to the image repository | Check | |
| Trigger Zadig Workflow | Trigger other Zadig workflows | Check | |
| Offline Service | Delete service-related resources from the specified environment | Check |
# Trigger
Supported trigger types:
| Required | Description | Configuration and Usage |
|---|---|---|
| Git Trigger | Automatically trigger the workflow after code changes | Check |
| Timer | Schedule the workflow to trigger at a specific time | Check |
| JIRA Trigger | Automatically trigger the workflow after JIRA issue status changes | Check |
| Feishu Project Trigger | Automatically trigger the workflow after Feishu project status changes | Check |
| Universal Trigger | Third-party systems can automatically trigger the workflow through webhooks | Check |
# Notification
Workflows support notifications to Feishu, Enterprise WeChat, and DingTalk groups. For specific configuration and usage, see Workflow Notifications
# Workflow View
Organize workflows in different views for quick preview and use.
Enter the project -> workflow, click the View tab to view the workflow information in the current view, and click the + button to create a new view.
- Only system administrators and project administrators can perform
Create View,Edit View, andDelete Viewoperations - The
Allview contains all workflows under the current project and cannot be deleted - After creating a new workflow in a view, the workflow will automatically belong to the current view




