DataWorks:Deploy nodes

Usage notes

• The time when a node is deployed affects the time when the instances that are generated for the node take effect. If you deploy a node during the period from 23:30 to 24:00 on the current day, instances that are generated for the node take effect on the third day after the deployment regardless of whether the Instance Generation Mode parameter for the node is set to Next Day or Immediately After Deployment. For more information about the instance generation mode, see Configure immediate instance generation for a node.

• Users who want to deploy nodes must be grant the required permissions. Developers can create deployment tasks for nodes that need to be deployed, but only users who are granted the O&M permissions can deploy the nodes.

• You can manage a node deployment process. Whether the deployment operation is successful depends on the permissions of the role that is used to perform the operation and the specified deployment process. If the deployment operation fails, you can check the status of the deployment task on the Deploy Tasks page.

• You can deploy a node only after the node is committed. A node can enter the to-be-deployed state on the Create Deploy Task page only if the node is committed.

Deploy a node in a workspace that is in standard mode

1. Go to the DataStudio page.

   Log on to the DataWorks console. In the left-side navigation pane, choose Data Modeling and Development > DataStudio. On the page that appears, select the desired workspace from the drop-down list and click Go to DataStudio.

2. Deploy a node.

   After a node passes the built-in checks, you can go to the Create Deploy Task page and deploy the node on which a change operation is performed to the production environment. The following deployment methods are supported:

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

   • To deploy multiple nodes at a time, select the nodes and click Add to List in the lower part of the Create Deploy Task page.

   Note

   • Developers can create deployment tasks for nodes that need to be deployed, but only users who are granted the O&M permissions can deploy the nodes on the Deploy Tasks page.

   • If you enable a check for a node, the node can be deployed only after the node passes the check.

3. View the deployment result.

   After you click Deploy, you can view the deployment result on the Deploy Tasks page.

   Note

   Whether the deployment operation is successful depends on the permissions of the role that is used to perform the operation and the specified deployment process. If the deployment operation fails, you can check the status of the deployment task on the Deploy Tasks page.

4. Cancel the deployment.

   If a node does not need to be deployed or fails to be deployed, you can perform the following operations to cancel the deployment:

   • To cancel the deployment of a node that waits to be deployed, click Cancel Deployment in the Actions column of the node on the Create Deploy Task page.

   • To cancel the deployment of a node that fails to be deployed, click View Details in the Actions column of the node on the Deploy Tasks page, and then click Cancel Deployment.

5. View the version details of the node to be deployed.

   You can go to the Create Deploy Task page, find the node whose version details you want to view, and then click View in the Actions column to go to the Compare Versions page. On the Compare Versions page, you can compare the version of the node to be deployed with the version of the node that is already run in the production environment, and you can view the differences between the code or scheduling configurations of the versions of the node. You can switch between different versions of the node for comparison.

   For more information about the parameters that are related to version comparison, see Compare the versions of a node.