All Products
Search

This Product

    DataWorks:Deploy nodes

    Document Center

    DataWorks:Deploy nodes

    Last Updated:Jun 17, 2026

    This topic describes how to deploy nodes in a workspace that is in standard mode.

    Prerequisites

    • Make sure that the node is submitted before you deploy it.

    • Make sure that the node is associated with compute resources. If the Compute Resource drop-down list in the node schedule settings is empty, go to the workspace management page and associate the required compute resources with Data Studio.

    Background

    In a basic mode workspace, submitted tasks are automatically scheduled in the production environment. In a standard mode workspace, submitted tasks only take effect in the development environment and are not automatically scheduled. You must deploy the tasks to the production environment through the deployment process before they are periodically scheduled.

    Note

    After you submit operations in Data Studio, they are listed on the deployment page with a to-be-deployed status. From there, you can deploy them to the production environment.

    1. DataWorks provides the following pre-deployment checks:

      • Code review: You can enable mandatory code review for a workspace. If enabled, a node must pass the code review before it can be deployed. For more information, see Code review.

      • Smoke testing: You can enable mandatory smoke testing for a workspace. If enabled, a node must pass smoke testing before it can be deployed. For more information, see Perform smoke testing.

      • Extensions: You can enable extension validation for a workspace. If enabled, a node must pass the extension validation before it can be deployed. For more information, see Extensions overview.

      • Check items: You can enable checks for specific items in the Data Governance Center. If enabled, a node must meet the check item requirements before it can be deployed. For more information, see Configure check items.

    2. DataWorks supports the following deployment scenarios:

      • Standard mode deployment: In a standard mode workspace, you can deploy nodes from the development environment to the production environment.

      • Cross-workspace deployment: In basic mode, you can deploy nodes between workspaces that are in the same region and under the same Alibaba Cloud account.

      • Cross-cloud deployment: You can deploy nodes across different Alibaba Cloud accounts, regions, or cloud platforms, such as Alibaba Finance Cloud and Alibaba Gov Cloud.

    Usage notes

    • The time at which you deploy a task affects when the deployment takes effect on instances. Changes made during the full instance generation period (23:30 to 24:00 each day), regardless of whether instances are generated on T+1 or immediately after deployment, do not take effect until the third day after the operation. For more information about instance generation, see Instance generation overview.

    • Deployment is subject to permission control. Developers can package to-be-deployed operations, but only users with operator permissions can deploy the packages.

    • Deployment is subject to process controls. Deployment operations are constrained by role permissions and process controls, and deployment may not always succeed. Make sure that the task is successfully deployed. If the deployment does not succeed, check the deployment package status on the The deploy task page.

    • Only submitted operations can be deployed. Only submitted operations are listed on the deployment page with a to-be-deployed status.

    Deployment process for a standard mode workspace

    1. Go to the Data Studio page.

      Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.

    2. Deploy the task.

      File change operations that pass the checks can be deployed to the production environment on the Deploy > Create Deploy Task page. The following two deployment methods are available:

      • Deploy a single item: Click the Deploy button in the Actions column of the item to deploy it.

      • Deploy items in a batch: Select multiple items and click Add to List at the bottom to deploy them to the production environment in a batch.

      Note

      • Developers can package to-be-deployed operations, but a user with operator permissions must go to the Deployment Packages page to deploy the package.

      • If you want to perform pre-deployment checks, the to-be-deployed tasks must be in a check-passed state before they can be deployed.

    3. View the deployment result.

      After you click Deploy, you can view the deployment result on the Deploy > Deployment Packages page.

      Note

      Deployment operations are constrained by role permissions and process controls, and deployment may not always succeed. Make sure that the task is successfully deployed. If the deployment does not succeed, check the deployment package status on the deployment packages page.

    4. Cancel a deployment.

      If you do not need to deploy a task or the deployment fails, you can perform the following operations:

      • For tasks in the to-be-deployed state, you can cancel the deployment on the Deploy > Create Deploy Task page.

      • For tasks that fail during batch deployment, you can go to the Deploy > Deployment Packages page, click to view the details of the failed deployment package, and then click the Revoke button to cancel the deployment.

    5. View version details of a to-be-deployed file.

      On the Deploy > Create Deploy Task page, click View in the Actions column of an item to go to the Diff page. On this page, you can compare the to-be-deployed file version with the version in the production environment and view the differences in code or schedule settings between versions. You can also switch to a different version for comparison.

      For more information about the parameters on the Diff page, see Diff parameters.