In a rigorous data development process, developers develop and debug code and configure dependencies and scheduling properties for nodes in the development environment. Then, developers commit and deploy the nodes to run them in the production environment.

DataWorks workspaces in standard mode can process data seamlessly from the development environment to the production environment within a single workspace. We recommend that you use workspaces in standard mode to develop and produce data.

Deploy nodes in a workspace in standard mode

Each DataWorks workspace in standard mode is associated with two MaxCompute projects, one as the development environment and the other as the production environment. You can directly commit and deploy nodes from the development environment to the production environment.Deploy nodes in a workspace in standard mode
To deploy nodes in a workspace in standard mode, follow these steps:
  1. After you configure and debug nodes, click the Submit icon. DataWorks automatically checks the dependencies between nodes.Submit
    Note If all nodes of a workflow are committed and you only modify the workflow or node properties, you do not need to select the nodes. If a node is committed but the node code is not changed, the node cannot be selected again. In this case, you can enter the description and commit the workflow. The changes are automatically committed.
  2. After you commit the nodes, click the Deploy icon.
  3. On the Create Deploy Task page that appears, select the nodes to deploy and click Add to List. The nodes are added to To-Be-Deployed Node List.
    You can filter the nodes by committer, node type, change type, commission time, node name, and node ID. If you click Deploy Selected, the selected nodes are deployed to the production environment immediately.Deploy selected nodes
  4. Click To-Be-Deployed Node List in the upper-right corner. In the Nodes to Deploy pane that appears, verify that the node information in the list is correct and click Deploy All. All nodes in the list are deployed to the production environment.Deploy all nodes
    Note Workspaces in standard mode do not allow you to directly perform operations on table data in the production environment. This guarantees a stable, secure, and reliable production environment. Therefore, we recommend that you deploy and run nodes in a workspace in standard mode.

Clone nodes between workspaces in basic mode

You cannot deploy nodes in workspaces in basic mode. If you want to isolate the development environment from the production environment for workspaces in basic mode, create two workspaces, one for development and the other for production. You can clone nodes from the development workspace to the production workspace.

As shown in the following figure, two workspaces in basic mode are created, one for development and the other for production. You can use the cross-workspace cloning feature to clone nodes from Workspace A to Workspace B, and then commit the cloned nodes to the scheduler for scheduling.Clone nodes
Note
  • Permission requirement: Only workspace administrators and Resource Access Management (RAM) users who are assigned the administration expert role can clone nodes.
  • Workspace type: You can only clone nodes in workspaces in basic mode, but cannot clone those in workspaces in standard mode.
  • Prerequisites: The source workspace in basic mode and the destination workspace in standard mode are created.
  1. Commit nodes.
    After you create and configure nodes in the source workspace, commit the nodes on the dashboard of the target workflow.Commit nodes
  2. Click Cross-project cloning in the upper-right corner.Clone nodes across workspaces
  3. Set the destination workspace, select the committed node to be cloned, and click Add to List.Add to List
  4. Clone the nodes.

    Click View List. Verify that the node information is correct and click Clone All.

    In the Create Clone Task dialog box that appears, click Clone. The selected nodes are cloned.

  5. View the cloned nodes.
    You can view the cloned nodes on the Release Package page of the source workspace.Cloned nodes

    Switch to the destination workspace. You can find that the nodes are cloned from the source workspace.

Note For more information about how to process node dependencies during node cloning, see Cross-project cloning.