tencent cloud

Tencent Cloud WeData

DocumentationTencent Cloud WeDataOperation GuideData DevelopmentTask ReleaseRelease Mode Description

Release Mode Description

Download
Focus Mode
Font Size
Last updated: 2026-05-29 14:45:20

Overview

WeData provides multiple release modes to isolate development and production environments, meeting requirements for different security levels and operational efficiency. This document helps you understand the core differences, applicable scenarios, and isolation capabilities of each release mode, enabling you to select an appropriate solution based on your actual business needs.
Note:
Different release modes have different prerequisite requirements for the project mode and environment deployment. Confirm the appropriate release mode before setting up the environment.

Release Mode Overview

WeData supports the following four release modes:
Release Mode
Feature Name
Core Features
Cross-environment release (import/export)
Migration Assistant
Migrates tasks across projects via import/export, supporting cross-account and cross-region operations.
CI/CD
WeData Bundle
Implements continuous integration and delivery via Git + automated pipelines, supporting cross-project and cross-account operations.

Core Differences Comparison

Level
Cross-Environment Release (Import/Export)
CI/CD
Feature Name
Migration Assistant
WeData Bundle
Project Mode Requirement
Simple mode
Simple mode
Number of Projects
Two or more projects (can be across accounts)
Two or more projects (can be across accounts)
Cross-Region Support
Supported
Supported
Cross-Account Support
Supported
Supported
Version Management
Has release records, but does not support rollback.
Git version control
Degree of Automation
Manual export and import
Automated pipeline triggering
Approval Process
No built-in approval
Can be implemented via Git merge request approval.
Workflow Scheduling Mode Support
Not supported.
Supported

Isolation Capability Comparison

Isolation Dimension
Cross-Environment Release (Import/Export)
CI/CD
Network
Physical isolation.
Supports both cross-project and cross-environment modes. The isolation scenarios correspond to cross-project cloning and cross-environment publishing, respectively.
User Account
Physical isolation.
Same as above.
Computing Resource
Physical isolation.
Same as above.
Storage Resource
Physical isolation.
Same as above.
Task ID
Physical isolation.
Same as above.
Task Code/Configuration
Physical isolation.
Same as above.
Project Member
Physical isolation.
Same as above.
Project Parameter
Physical isolation.
Same as above.
Execution Resource Group
Physical isolation.
Same as above.
Data Source Configuration
Physical isolation.
Same as above.

Cost and Security Comparison

Level
Cross-Environment Release (Import/Export)
CI/CD
Deployment cost
Medium to High (1 or multiple sets of WeData + corresponding engines)
Medium (1 or multiple sets of WeData + 2 or more engines + Git service)
Security level
High (Complete physical isolation).
Medium-High (data physically isolated + Git managed)

Environment Preparation Instructions

Cross-Environment Release (Import and Export)

Deploy two sets of WeData products (across accounts and regions).
Deploy two big data engines.
Create one simple-mode project respectively.

CI/CD

Deploy one set of WeData products.
Deploy one or two big data engines.
Create one or two projects (by configuring the dev/prod targets in wedata.yml).
Set up a Git repository (such as GitLab and GitHub).
Configure a CI/CD pipeline (for example, .gitlab-ci.yml).

Release Mode Selection Recommendations

1. Select cross-environment release (import/export):
For scenarios with high security requirements involving security-sensitive data.
Developers are not allowed to access the production environment, which requires complete physical isolation.
Full isolation across the control, task, and data layers.
Accept higher deployment and maintenance costs and lower operational efficiency.
2. Select CI/CD:
The team is familiar with the Git workflow and aims to manage task configurations through code version control.
Require an automated continuous integration and delivery process.
Aim to control the release cadence using a Git branch policy (e.g., dev/prod).
Require flexible deployment capabilities across projects and even accounts.
Previous Topic: Recycle BinNext Topic: CI/CD — Continuous Integration and Delivery

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback