DataWorks:Deploy nodes

Prerequisites

Before you begin, ensure that you have:

• A committed node — only committed nodes can enter the to-be-deployed state on the Create Deploy Task page

• Developer or Operations & Maintenance (O&M) role access — developers can create deployment tasks; only users with O&M permissions can execute the deployment on the Deploy Tasks page

How deployment works

DataWorks separates development and production environments to prevent untested changes from affecting scheduled production jobs.

All committed changes on the DataStudio page enter the to-be-deployed state on the Create Deploy Task page. Only file-related operations can be deployed to production from this page.

DataWorks supports three deployment scenarios:

This topic covers deployment within a standard mode workspace.

Usage notes

• Deployment timing affects instance scheduling. If you deploy a node between 23:30 and 24:00, the generated instances take effect on the third day after deployment — regardless of whether Instance Generation Mode is set to Next Day or Immediately After Deployment. For details, see Configure immediate instance generation for a task.

• Pre-deployment checks may block deployment. If your workspace has checks enabled, a node must pass all required checks before it can be deployed. The following checks are available:

  Check type	How it is enabled	Reference
  Code review	Enable the forcible code review feature for the workspace	Code review
  Smoke testing	Enable the forcible smoke testing feature for the workspace	Perform smoke testing
  Extension-based check	Enable the extension-based check feature for the workspace	Overview
  Check item-based check	Configure a check item for the node in Data Governance Center	Configure check items

Deploy a node to production

1. Go to the DataStudio page. Log on to the DataWorks console. In the top navigation bar, select a region. In the left-side navigation pane, choose Data Development and O&M > Data Development. Select a workspace from the drop-down list and click Go to Data Development.

2. Open the Create Deploy Task page and deploy the node. After a node passes all required built-in checks, it appears on the Create Deploy Task page. Two deployment methods are available:

   • To deploy a single node, click Deploy in the Actions column of the node.

   • To deploy multiple nodes at once, select the nodes and click Add to List at the bottom of the page.

   Only users with O&M permissions can execute the deployment on the Deploy Tasks page.

3. View the deployment result on the Deploy Tasks page. After clicking Deploy, go to the Deploy Tasks page to check the deployment status. If the deployment fails, review the task status to identify the cause.

4. (Optional) Cancel a deployment.

   • Node waiting to be deployed: On the Create Deploy Task page, click Cancel Deployment in the Actions column.

   • Node that failed to deploy: On the Deploy Tasks page, click View Details in the Actions column, then click Cancel Deployment.

5. (Optional) Compare node versions before deploying. On the Create Deploy Task page, click View in the Actions column to open the Compare Versions page. This page shows the differences in code and scheduling configurations between the version to be deployed and the version currently running in production. Switch between versions to compare them. For parameter details, see Compare the versions of a node.

What's next

After deploying a node, verify that it is running as expected in the production environment:

• On the Deploy Tasks page, confirm the deployment status is successful.

• Check the scheduled instances to confirm they are generated and running at the expected times.

• If the node fails to deploy or schedule correctly, review the role permissions and the configured deployment process, or cancel the deployment and re-deploy after resolving the issue.