You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by zh...@apache.org on 2022/03/21 10:42:43 UTC
[dolphinscheduler-website] branch master updated: Change how to release python dist (#744)
This is an automated email from the ASF dual-hosted git repository.
zhongjiajie pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new 2d4f8d3 Change how to release python dist (#744)
2d4f8d3 is described below
commit 2d4f8d338e80b7f6e5de9e4a34434327c2ad0ed0
Author: Jiajie Zhong <zh...@hotmail.com>
AuthorDate: Mon Mar 21 18:42:36 2022 +0800
Change how to release python dist (#744)
* Change how to release python dist
* Fix dead link
---
.github/workflows/dead-link-checker.yaml | 2 +-
community/en-us/release.md | 13 ++++++++-----
community/zh-cn/DSIP.md | 2 +-
community/zh-cn/release.md | 14 +++++++++-----
docs/en-us/1.2.0/user_doc/system-manual.md | 4 ++--
docs/en-us/1.2.1/user_doc/system-manual.md | 4 ++--
docs/en-us/1.3.1/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.2/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.3/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.4/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.5/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.6/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.8/user_doc/system-manual.md | 16 +++++++++-------
docs/en-us/1.3.9/user_doc/system-manual.md | 16 +++++++++-------
.../2.0.0/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 22 +++++++++++-----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.1/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 22 +++++++++++-----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.2/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 22 +++++++++++-----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 22 +++++++++++-----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.5/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 22 +++++++++++-----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../dev/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 22 +++++++++++-----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
docs/zh-cn/1.2.0/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.2.1/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.1/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.2/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.3/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.4/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.5/user_doc/kubernetes-deployment.md | 2 +-
docs/zh-cn/1.3.5/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.6/user_doc/docker-deployment.md | 2 +-
docs/zh-cn/1.3.6/user_doc/kubernetes-deployment.md | 4 ++--
docs/zh-cn/1.3.6/user_doc/system-manual.md | 14 ++++++++------
docs/zh-cn/1.3.8/user_doc/docker-deployment.md | 2 +-
docs/zh-cn/1.3.8/user_doc/kubernetes-deployment.md | 4 ++--
docs/zh-cn/1.3.8/user_doc/system-manual.md | 17 ++++++++++-------
docs/zh-cn/1.3.9/user_doc/docker-deployment.md | 2 +-
docs/zh-cn/1.3.9/user_doc/kubernetes-deployment.md | 4 ++--
docs/zh-cn/1.3.9/user_doc/system-manual.md | 18 ++++++++++--------
.../2.0.0/user_doc/guide/installation/docker.md | 2 +-
.../user_doc/guide/installation/kubernetes.md | 4 ++--
.../2.0.0/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 18 +++++++++---------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.1/user_doc/guide/installation/docker.md | 2 +-
.../user_doc/guide/installation/kubernetes.md | 4 ++--
.../2.0.1/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 20 ++++++++++----------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.2/user_doc/guide/installation/docker.md | 2 +-
.../user_doc/guide/installation/kubernetes.md | 4 ++--
.../2.0.2/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 18 +++++++++---------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.3/user_doc/guide/installation/docker.md | 2 +-
.../user_doc/guide/installation/kubernetes.md | 4 ++--
.../2.0.3/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 18 +++++++++---------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../2.0.5/user_doc/guide/installation/docker.md | 2 +-
.../user_doc/guide/installation/kubernetes.md | 4 ++--
.../2.0.5/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 16 ++++++++--------
.../user_doc/guide/project/workflow-instance.md | 2 +-
.../dev/user_doc/guide/installation/kubernetes.md | 4 ++--
.../dev/user_doc/guide/project/task-instance.md | 2 +-
.../user_doc/guide/project/workflow-definition.md | 18 +++++++++---------
.../user_doc/guide/project/workflow-instance.md | 2 +-
docs/zh-cn/dev/user_doc/guide/start/docker.md | 2 +-
78 files changed, 350 insertions(+), 306 deletions(-)
diff --git a/.github/workflows/dead-link-checker.yaml b/.github/workflows/dead-link-checker.yaml
index ee5f7d5..58f3667 100644
--- a/.github/workflows/dead-link-checker.yaml
+++ b/.github/workflows/dead-link-checker.yaml
@@ -29,7 +29,7 @@ jobs:
timeout-minutes: 30
steps:
- uses: actions/checkout@v2
- - run: sudo npm install -g markdown-link-check@3.9.3
+ - run: sudo npm install -g markdown-link-check@3.10.0
- run: |
for file in $(find . -name "*.md"); do
markdown-link-check -c .dlc.json -q "$file"
diff --git a/community/en-us/release.md b/community/en-us/release.md
index cfd84a3..8b6e668 100644
--- a/community/en-us/release.md
+++ b/community/en-us/release.md
@@ -142,10 +142,13 @@ git push origin ${RELEASE.VERSION}-release
### Pre-Release Check
```shell
-mvn release:prepare -Prelease -Darguments="-DskipTests" -DautoVersionSubmodules=true -DdryRun=true -Dusername=${Github username}
+# make gpg command could be run in maven correct
+export GPG_TTY=$(tty)
+
+mvn release:prepare -Prelease,python -Darguments="-DskipTests" -DautoVersionSubmodules=true -DdryRun=true -Dusername=${Github username}
```
--Prelease: choose release profile, which will pack all the source codes, jar files and executable binary packages.
+-Prelease,python: choose release and python profile, which will pack all the source codes, jar files and executable binary packages, and Python distribute package.
-DautoVersionSubmodules=true：it can make the version number is inputted only once and not for each sub-module.
@@ -162,7 +165,7 @@ mvn release:clean
Then, prepare to execute the release.
```shell
-mvn release:prepare -Prelease -Darguments="-DskipTests" -DautoVersionSubmodules=true -DpushChanges=false -Dusername=${Github username}
+mvn release:prepare -Prelease,python -Darguments="-DskipTests" -DautoVersionSubmodules=true -DpushChanges=false -Dusername=${Github username}
```
It is basically the same as the previous rehearsal command, but deleting -DdryRun=true parameter.
@@ -179,7 +182,7 @@ git push origin --tags
### Deploy the Release
```shell
-mvn release:perform -Prelease -Darguments="-DskipTests" -DautoVersionSubmodules=true -Dusername=${Github username}
+mvn release:perform -Prelease,python -Darguments="-DskipTests" -DautoVersionSubmodules=true -Dusername=${Github username}
```
After that command is executed, the version to be released will be uploaded to Apache staging repository automatically.
@@ -300,7 +303,7 @@ gpg --verify python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.
#### Check source package
-Decompress `apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz` and check the following items:
+Decompress `apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz` and `apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz` in `python` directory then check the following items:
* Check whether source tarball is oversized for including nonessential files
* `LICENSE` and `NOTICE` files exist
diff --git a/community/zh-cn/DSIP.md b/community/zh-cn/DSIP.md
index 536e837..520ffc1 100644
--- a/community/zh-cn/DSIP.md
+++ b/community/zh-cn/DSIP.md
@@ -47,7 +47,7 @@ integer in [All DSIPs][all-DSIPs] issues.
下面是邮件的模板
- 标题: `[DISCUSS][DSIP-XXX] <CHANGE-TO-YOUR-LOVELY-PROPOSAL-TITLE>`, 将 `XXX` 修改为 to special integer you just change in
- [GitHub Issue](#create-github-issue), and also change proposal title.
+ GitHub Issue, and also change proposal title.
- 内容:
```text
diff --git a/community/zh-cn/release.md b/community/zh-cn/release.md
index 686255d..eda3c9c 100644
--- a/community/zh-cn/release.md
+++ b/community/zh-cn/release.md
@@ -152,10 +152,14 @@ git push origin ${RELEASE.VERSION}-release
### 发布预校验
```shell
-mvn release:prepare -Prelease -Darguments="-DskipTests" -DautoVersionSubmodules=true -DdryRun=true -Dusername=${Github用户名}
+# 保证 python profile 的 gpg 可以正常运行
+export GPG_TTY=$(tty)
+
+# 运行发版校验
+mvn release:prepare -Prelease,python -Darguments="-DskipTests" -DautoVersionSubmodules=true -DdryRun=true -Dusername=${Github用户名}
```
--Prelease: 选择release的profile，这个profile会打包所有源码、jar文件以及可执行二进制包。
+-Prelease,python: 选择release和python的profile，这个profile会打包所有源码、jar文件以及可执行二进制包，以及Python的二进制包。
-DautoVersionSubmodules=true：作用是发布过程中版本号只需要输入一次，不必为每个子模块都输入一次。
@@ -172,7 +176,7 @@ mvn release:clean
然后准备执行发布。
```shell
-mvn release:prepare -Prelease -Darguments="-DskipTests" -DautoVersionSubmodules=true -DpushChanges=false -Dusername=${Github用户名}
+mvn release:prepare -Prelease,python -Darguments="-DskipTests" -DautoVersionSubmodules=true -DpushChanges=false -Dusername=${Github用户名}
```
和上一步演练的命令基本相同，去掉了-DdryRun=true参数。
@@ -199,7 +203,7 @@ git push origin --tags
### 部署发布
```shell
-mvn release:perform -Prelease -Darguments="-DskipTests" -DautoVersionSubmodules=true -Dusername=${Github用户名}
+mvn release:perform -Prelease,python -Darguments="-DskipTests" -DautoVersionSubmodules=true -Dusername=${Github用户名}
```
执行完该命令后，待发布版本会自动上传到Apache的临时筹备仓库(staging repository)。
@@ -319,7 +323,7 @@ gpg --verify python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.
#### 检查源码包的文件内容
-解压缩`apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz`，进行如下检查:
+解压缩`apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz`以及Python文件夹下的`apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz`，进行如下检查:
- 检查源码包是否包含由于包含不必要文件，致使tarball过于庞大
- 存在`LICENSE`和`NOTICE`文件
diff --git a/docs/en-us/1.2.0/user_doc/system-manual.md b/docs/en-us/1.2.0/user_doc/system-manual.md
index 45f90c3..6ac831d 100644
--- a/docs/en-us/1.2.0/user_doc/system-manual.md
+++ b/docs/en-us/1.2.0/user_doc/system-manual.md
@@ -31,7 +31,7 @@ The homepage contains task status statistics, process status statistics, and wor
- Fill in the Node Name, Description, and Script fields.
- Selecting "task priority" will give priority to high-level tasks in the execution queue. Tasks with the same priority will be executed in the first-in-first-out order.
- Timeout alarm. Fill in "Overtime Time". When the task execution time exceeds the overtime, it can alarm and fail over time.
- - Fill in "Custom Parameters" and refer to [Custom Parameters](#CustomParameters)
+ - Fill in "Custom Parameters" and refer to [Custom Parameters](#CustomParameters) <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/process_definitions_en.png" width="80%" />
</p>
@@ -52,7 +52,7 @@ The homepage contains task status statistics, process status statistics, and wor
<img src="/img/global_parameters_en.png" width="80%" />
</p>
- - For other types of nodes, refer to [task node types and parameter settings](#TaskNodeType)
+ - For other types of nodes, refer to [task node types and parameter settings](#TaskNodeType) <!-- markdown-link-check-disable-line -->
### Execution process definition
- **The process definition of the off-line state can be edited, but not run**, so the on-line workflow is the first step.
diff --git a/docs/en-us/1.2.1/user_doc/system-manual.md b/docs/en-us/1.2.1/user_doc/system-manual.md
index bd6a5dc..4d975f5 100644
--- a/docs/en-us/1.2.1/user_doc/system-manual.md
+++ b/docs/en-us/1.2.1/user_doc/system-manual.md
@@ -31,7 +31,7 @@ The homepage contains task status statistics, process status statistics, and wor
- Fill in the Node Name, Description, and Script fields.
- Selecting "task priority" will give priority to high-level tasks in the execution queue. Tasks with the same priority will be executed in the first-in-first-out order.
- Timeout alarm. Fill in "Overtime Time". When the task execution time exceeds the overtime, it can alarm and fail over time.
- - Fill in "Custom Parameters" and refer to [Custom Parameters](#CustomParameters)
+ - Fill in "Custom Parameters" and refer to [Custom Parameters](#CustomParameters) <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/process_definitions_en.png" width="80%" />
</p>
@@ -52,7 +52,7 @@ The homepage contains task status statistics, process status statistics, and wor
<img src="/img/global_parameters_en.png" width="80%" />
</p>
- - For other types of nodes, refer to [task node types and parameter settings](#TaskNodeType)
+ - For other types of nodes, refer to [task node types and parameter settings](#TaskNodeType) <!-- markdown-link-check-disable-line -->
### Execution process definition
- **The process definition of the off-line state can be edited, but not run**, so the on-line workflow is the first step.
diff --git a/docs/en-us/1.3.1/user_doc/system-manual.md b/docs/en-us/1.3.1/user_doc/system-manual.md
index 86fb925..945b2cb 100644
--- a/docs/en-us/1.3.1/user_doc/system-manual.md
+++ b/docs/en-us/1.3.1/user_doc/system-manual.md
@@ -48,6 +48,7 @@ Add a Shell task to the drawing board, as shown in the figure below:
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (not required): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). The resource file is a file created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the resource call command in the script is `sh test.sh`;
+ <!-- markdown-link-check-disable-next-line -->
6. Custom parameters (not required), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
@@ -62,22 +63,23 @@ Add a Shell task to the drawing board, as shown in the figure below:
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save the workflow definition：** Click the "Save" button, and the "Set DAG Diagram Name" pop-up box will pop up, as shown in the figure below, enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [Custom Parameters](#UserDefinedParameters)) , Click the "Add" button, the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
- > For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+ > For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown below:
<p align="center">
<img src="/img/work_list_en.png" width="80%" />
</p>
The operation functions of the workflow definition list are as follows:
- - **edit：** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+ - **edit：** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).<!-- markdown-link-check-disable-line -->
- **online：** When the workflow status is "offline", the workflow is online. Only the workflow in the "online" state can run, but cannot be edited.
- **Offline：** When the workflow status is "online", the offline workflow and the offline workflow can be edited but not run。
- - **run：** Only online workflows can run. See [2.3.3 Run Workflow] for the operation steps(#runWorkflow)
- - **timing：** Only the online workflow can set the timing, and the system automatically schedules the workflow to run regularly. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. For timing operation steps, please refer to [2.3.4 Workflow Timing](#creatTiming).
+ - **run：** Only online workflows can run. See [2.3.3 Run Workflow] for the operation steps(#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **timing：** Only the online workflow can set the timing, and the system automatically schedules the workflow to run regularly. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. For timing operation steps, please refer to [2.3.4 Workflow Timing](#creatTiming). <!-- markdown-link-check-disable-line -->
- **Timing management：** The timing management page can be edited, online/offline, and deleted.
- **delete：** Delete the workflow definition.
- **download：** Download the workflow definition to the local.
@@ -125,8 +127,8 @@ Add a Shell task to the drawing board, as shown in the figure below:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
- - Failure strategy, notification strategy, process priority, Worker grouping, notification group, recipient, and CC are the same [workflow running parameters](#runParamers)。
- - 点Click the "Create" button, and the timing is successfully created. At this time, the timing status is "**Offline**", and the timing needs to be **Online** to take effect.
+ - Failure strategy, notification strategy, process priority, Worker grouping, notification group, recipient, and CC are the same [workflow running parameters](#runParamers)。\. <!-- markdown-link-check-disable-line -->
+ - Click the "Create" button, and the timing is successfully created. At this time, the timing status is "**Offline**", and the timing needs to be **Online** to take effect.
- Timed online: Click the "Timing Management" button<img src="/img/timeManagement.png" width="35"/>，Enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the figure below, the workflow takes effect regularly.
<p align="center">
<img src="/img/time-manage-list-en.png" width="80%" />
@@ -150,7 +152,7 @@ Add a Shell task to the drawing board, as shown in the figure below:
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
- - Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+ - Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.2/user_doc/system-manual.md b/docs/en-us/1.3.2/user_doc/system-manual.md
index 15138d0..ca37388 100644
--- a/docs/en-us/1.3.2/user_doc/system-manual.md
+++ b/docs/en-us/1.3.2/user_doc/system-manual.md
@@ -53,7 +53,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished execute, tasks 2 and 3 will be executed simultaneously.
@@ -67,11 +68,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -82,11 +84,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -137,7 +139,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -167,7 +169,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.3/user_doc/system-manual.md b/docs/en-us/1.3.3/user_doc/system-manual.md
index 3553993..f7c635f 100644
--- a/docs/en-us/1.3.3/user_doc/system-manual.md
+++ b/docs/en-us/1.3.3/user_doc/system-manual.md
@@ -54,7 +54,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished execute, tasks 2 and 3 will be executed simultaneously.
@@ -68,11 +69,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -83,11 +85,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -138,7 +140,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -168,7 +170,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.4/user_doc/system-manual.md b/docs/en-us/1.3.4/user_doc/system-manual.md
index e97424a..159f637 100644
--- a/docs/en-us/1.3.4/user_doc/system-manual.md
+++ b/docs/en-us/1.3.4/user_doc/system-manual.md
@@ -54,7 +54,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished execute, tasks 2 and 3 will be executed simultaneously.
@@ -68,11 +69,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -83,11 +85,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -139,7 +141,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -169,7 +171,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.5/user_doc/system-manual.md b/docs/en-us/1.3.5/user_doc/system-manual.md
index e64751b..5ee45fb 100644
--- a/docs/en-us/1.3.5/user_doc/system-manual.md
+++ b/docs/en-us/1.3.5/user_doc/system-manual.md
@@ -54,7 +54,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished execute, tasks 2 and 3 will be executed simultaneously.
@@ -68,11 +69,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -83,11 +85,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -139,7 +141,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -169,7 +171,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.6/user_doc/system-manual.md b/docs/en-us/1.3.6/user_doc/system-manual.md
index 5d44e5d..1ee5ccf 100644
--- a/docs/en-us/1.3.6/user_doc/system-manual.md
+++ b/docs/en-us/1.3.6/user_doc/system-manual.md
@@ -52,7 +52,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished execute, tasks 2 and 3 will be executed simultaneously.
@@ -66,11 +67,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -81,11 +83,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -137,7 +139,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -167,7 +169,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.8/user_doc/system-manual.md b/docs/en-us/1.3.8/user_doc/system-manual.md
index 39f65d7..0cdda41 100644
--- a/docs/en-us/1.3.8/user_doc/system-manual.md
+++ b/docs/en-us/1.3.8/user_doc/system-manual.md
@@ -54,7 +54,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished execute, tasks 2 and 3 will be executed simultaneously.
@@ -68,11 +69,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -83,11 +85,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -139,7 +141,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -169,7 +171,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/1.3.9/user_doc/system-manual.md b/docs/en-us/1.3.9/user_doc/system-manual.md
index 823a289..d1e1c35 100644
--- a/docs/en-us/1.3.9/user_doc/system-manual.md
+++ b/docs/en-us/1.3.9/user_doc/system-manual.md
@@ -53,7 +53,8 @@ The home page contains task status statistics, process status statistics, and wo
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+<!-- markdown-link-check-disable-next-line -->
+6. Customize parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished executing, tasks 2 and 3 will be executed simultaneously.
@@ -67,11 +68,12 @@ The home page contains task status statistics, process status statistics, and wo
<img src="/img/dag7.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
#### 2.3.2 Workflow definition operation function
@@ -82,11 +84,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag). <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps. <!-- markdown-link-check-disable-line -->
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps. <!-- markdown-link-check-disable-line -->
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -138,7 +140,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers). <!-- markdown-link-check-disable-line -->
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
@@ -168,7 +170,7 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.0/user_doc/guide/project/task-instance.md b/docs/en-us/2.0.0/user_doc/guide/project/task-instance.md
index 6d02cdc..49280f5 100644
--- a/docs/en-us/2.0.0/user_doc/guide/project/task-instance.md
+++ b/docs/en-us/2.0.0/user_doc/guide/project/task-instance.md
@@ -6,7 +6,7 @@
<img src="/img/task-list-en.png" width="80%" />
</p>
-- <span id=taskLog>View log：</span>Click the "view log" button in the operation column to view the log of task execution.
+- View log：Click the "view log" button in the operation column to view the log of task execution.
<p align="center">
<img src="/img/task-log2-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.0/user_doc/guide/project/workflow-definition.md b/docs/en-us/2.0.0/user_doc/guide/project/workflow-definition.md
index ddb9d2f..e94dc21 100644
--- a/docs/en-us/2.0.0/user_doc/guide/project/workflow-definition.md
+++ b/docs/en-us/2.0.0/user_doc/guide/project/workflow-definition.md
@@ -1,6 +1,6 @@
# Workflow definition
-## <span id=creatDag> Create workflow definition</span>
+## Create workflow definition
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, and click the "Create Workflow" button to enter the **workflow DAG edit** page, as shown in the following figure:
<p align="center">
@@ -17,7 +17,7 @@
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished executing, tasks 2 and 3 will be executed simultaneously.
@@ -31,11 +31,11 @@
<img src="/img/dag7.png" width="80%" />
</p>
-- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
+- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [global parameters](../parameter/global.md)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
## Workflow definition operation function
@@ -46,12 +46,12 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#create-workflow-definition).
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#run-the-workflow) for the operation steps.
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#workflow-timing) for timing operation steps.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
- **Tree Diagram:** Display the task node type and task status in a tree structure, as shown in the figure below:
@@ -59,7 +59,7 @@ The operation functions of the workflow definition list are as follows:
<img src="/img/tree_en.png" width="80%" />
</p>
-## <span id=runWorkflow>Run the workflow</span>
+## Run the workflow
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button <img src="/img/online.png" width="35"/>，Go online workflow.
<p align="center">
@@ -70,7 +70,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
- <span id=runParamers>Description of workflow operating parameters:</span>
+ Description of workflow operating parameters:
* Failure strategy: When a task node fails to execute, other parallel task nodes need to execute the strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks being executed, and terminate the entire process.
* Notification strategy: When the process is over, the process execution information notification email is sent according to the process status, including any status is not sent, successful sent, failed sent, successful or failed sent.
@@ -91,7 +91,7 @@ The operation functions of the workflow definition list are as follows:
> Parallel mode: The tasks from May 1 to may 10 are executed simultaneously, and 10 process instances are generated on the process instance page.
-## <span id=creatTiming>Workflow timing</span>
+## Workflow timing
- Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, go online the workflow, click the "timing" button <img src="/img/timing.png" width="35"/> ,The timing parameter setting dialog box pops up, as shown in the figure below:
<p align="center">
@@ -102,7 +102,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
diff --git a/docs/en-us/2.0.0/user_doc/guide/project/workflow-instance.md b/docs/en-us/2.0.0/user_doc/guide/project/workflow-instance.md
index ac65ebe..4a8c909 100644
--- a/docs/en-us/2.0.0/user_doc/guide/project/workflow-instance.md
+++ b/docs/en-us/2.0.0/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](./task-instance.md)。
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.1/user_doc/guide/project/task-instance.md b/docs/en-us/2.0.1/user_doc/guide/project/task-instance.md
index 6d02cdc..49280f5 100644
--- a/docs/en-us/2.0.1/user_doc/guide/project/task-instance.md
+++ b/docs/en-us/2.0.1/user_doc/guide/project/task-instance.md
@@ -6,7 +6,7 @@
<img src="/img/task-list-en.png" width="80%" />
</p>
-- <span id=taskLog>View log：</span>Click the "view log" button in the operation column to view the log of task execution.
+- View log：Click the "view log" button in the operation column to view the log of task execution.
<p align="center">
<img src="/img/task-log2-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.1/user_doc/guide/project/workflow-definition.md b/docs/en-us/2.0.1/user_doc/guide/project/workflow-definition.md
index ddb9d2f..590d3e7 100644
--- a/docs/en-us/2.0.1/user_doc/guide/project/workflow-definition.md
+++ b/docs/en-us/2.0.1/user_doc/guide/project/workflow-definition.md
@@ -1,6 +1,6 @@
# Workflow definition
-## <span id=creatDag> Create workflow definition</span>
+## Create workflow definition
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, and click the "Create Workflow" button to enter the **workflow DAG edit** page, as shown in the following figure:
<p align="center">
@@ -17,7 +17,7 @@
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished executing, tasks 2 and 3 will be executed simultaneously.
@@ -31,11 +31,11 @@
<img src="/img/dag7.png" width="80%" />
</p>
-- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
+- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [global parameters](../parameter/global.md)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
## Workflow definition operation function
@@ -46,11 +46,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#create-workflow-definition).
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#run-the-workflow) for the operation steps.
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#workflow-timing) for timing operation steps.
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -59,7 +59,7 @@ The operation functions of the workflow definition list are as follows:
<img src="/img/tree_en.png" width="80%" />
</p>
-## <span id=runWorkflow>Run the workflow</span>
+## Run the workflow
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button <img src="/img/online.png" width="35"/>，Go online workflow.
<p align="center">
@@ -70,7 +70,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
- <span id=runParamers>Description of workflow operating parameters:</span>
+ Description of workflow operating parameters:
* Failure strategy: When a task node fails to execute, other parallel task nodes need to execute the strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks being executed, and terminate the entire process.
* Notification strategy: When the process is over, the process execution information notification email is sent according to the process status, including any status is not sent, successful sent, failed sent, successful or failed sent.
@@ -91,7 +91,7 @@ The operation functions of the workflow definition list are as follows:
> Parallel mode: The tasks from May 1 to may 10 are executed simultaneously, and 10 process instances are generated on the process instance page.
-## <span id=creatTiming>Workflow timing</span>
+## Workflow timing
- Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, go online the workflow, click the "timing" button <img src="/img/timing.png" width="35"/> ,The timing parameter setting dialog box pops up, as shown in the figure below:
<p align="center">
@@ -102,7 +102,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
diff --git a/docs/en-us/2.0.1/user_doc/guide/project/workflow-instance.md b/docs/en-us/2.0.1/user_doc/guide/project/workflow-instance.md
index ac65ebe..4a8c909 100644
--- a/docs/en-us/2.0.1/user_doc/guide/project/workflow-instance.md
+++ b/docs/en-us/2.0.1/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](./task-instance.md)。
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.2/user_doc/guide/project/task-instance.md b/docs/en-us/2.0.2/user_doc/guide/project/task-instance.md
index 6d02cdc..49280f5 100644
--- a/docs/en-us/2.0.2/user_doc/guide/project/task-instance.md
+++ b/docs/en-us/2.0.2/user_doc/guide/project/task-instance.md
@@ -6,7 +6,7 @@
<img src="/img/task-list-en.png" width="80%" />
</p>
-- <span id=taskLog>View log：</span>Click the "view log" button in the operation column to view the log of task execution.
+- View log：Click the "view log" button in the operation column to view the log of task execution.
<p align="center">
<img src="/img/task-log2-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.2/user_doc/guide/project/workflow-definition.md b/docs/en-us/2.0.2/user_doc/guide/project/workflow-definition.md
index ddb9d2f..02b0482 100644
--- a/docs/en-us/2.0.2/user_doc/guide/project/workflow-definition.md
+++ b/docs/en-us/2.0.2/user_doc/guide/project/workflow-definition.md
@@ -1,6 +1,6 @@
# Workflow definition
-## <span id=creatDag> Create workflow definition</span>
+## Create workflow definition
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, and click the "Create Workflow" button to enter the **workflow DAG edit** page, as shown in the following figure:
<p align="center">
@@ -17,7 +17,7 @@
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished executing, tasks 2 and 3 will be executed simultaneously.
@@ -31,11 +31,11 @@
<img src="/img/dag7.png" width="80%" />
</p>
-- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
+- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [global parameters](../parameter/global.md)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
## Workflow definition operation function
@@ -46,11 +46,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#create-workflow-definition).
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#run-the-workflow) for the operation steps.
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#workflow-timing) for timing operation steps.
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -59,7 +59,7 @@ The operation functions of the workflow definition list are as follows:
<img src="/img/tree_en.png" width="80%" />
</p>
-## <span id=runWorkflow>Run the workflow</span>
+## Run the workflow
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button <img src="/img/online.png" width="35"/>，Go online workflow.
<p align="center">
@@ -70,7 +70,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
- <span id=runParamers>Description of workflow operating parameters:</span>
+ Description of workflow operating parameters
* Failure strategy: When a task node fails to execute, other parallel task nodes need to execute the strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks being executed, and terminate the entire process.
* Notification strategy: When the process is over, the process execution information notification email is sent according to the process status, including any status is not sent, successful sent, failed sent, successful or failed sent.
@@ -91,7 +91,7 @@ The operation functions of the workflow definition list are as follows:
> Parallel mode: The tasks from May 1 to may 10 are executed simultaneously, and 10 process instances are generated on the process instance page.
-## <span id=creatTiming>Workflow timing</span>
+## Workflow timing
- Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, go online the workflow, click the "timing" button <img src="/img/timing.png" width="35"/> ,The timing parameter setting dialog box pops up, as shown in the figure below:
<p align="center">
@@ -102,7 +102,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
diff --git a/docs/en-us/2.0.2/user_doc/guide/project/workflow-instance.md b/docs/en-us/2.0.2/user_doc/guide/project/workflow-instance.md
index ac65ebe..4a8c909 100644
--- a/docs/en-us/2.0.2/user_doc/guide/project/workflow-instance.md
+++ b/docs/en-us/2.0.2/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](./task-instance.md)。
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.3/user_doc/guide/project/workflow-definition.md b/docs/en-us/2.0.3/user_doc/guide/project/workflow-definition.md
index 485c046..94fc56f 100644
--- a/docs/en-us/2.0.3/user_doc/guide/project/workflow-definition.md
+++ b/docs/en-us/2.0.3/user_doc/guide/project/workflow-definition.md
@@ -1,6 +1,6 @@
# Workflow Definition
-## <span id=creatDag> Create Workflow Definition</span>
+## Create workflow definition
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, and click the "Create Workflow" button to enter the **workflow DAG edit** page, as shown in the following figure:
<p align="center">
@@ -17,7 +17,7 @@
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished executing, tasks 2 and 3 will be executed simultaneously.
@@ -31,11 +31,11 @@
<img src="/img/dag7.png" width="80%" />
</p>
-- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
+- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [global parameters](../parameter/global.md)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
## Workflow Definition Operation Function
@@ -46,11 +46,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#create-workflow-definition).
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#run-the-workflow) for the operation steps.
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#workflow-timing) for timing operation steps.
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -59,7 +59,7 @@ The operation functions of the workflow definition list are as follows:
<img src="/img/tree_en.png" width="80%" />
</p>
-## <span id=runWorkflow>Run the Workflow</span>
+## Run the Workflow
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button <img src="/img/online.png" width="35"/>，Go online workflow.
<p align="center">
@@ -70,7 +70,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
- <span id=runParamers>Description of workflow operating parameters:</span>
+ Description of workflow operating parameters:
* Failure strategy: When a task node fails to execute, other parallel task nodes need to execute the strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks being executed, and terminate the entire process.
* Notification strategy: When the process is over, the process execution information notification email is sent according to the process status, including any status is not sent, successful sent, failed sent, successful or failed sent.
@@ -91,7 +91,7 @@ The operation functions of the workflow definition list are as follows:
> Parallel mode: The tasks from May 1 to may 10 are executed simultaneously, and 10 process instances are generated on the process instance page.
-## <span id=creatTiming>Workflow Timing</span>
+## Workflow Timing
- Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, go online the workflow, click the "timing" button <img src="/img/timing.png" width="35"/> ,The timing parameter setting dialog box pops up, as shown in the figure below:
<p align="center">
@@ -102,7 +102,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
diff --git a/docs/en-us/2.0.3/user_doc/guide/project/workflow-instance.md b/docs/en-us/2.0.3/user_doc/guide/project/workflow-instance.md
index 1733e7a..bfec717 100644
--- a/docs/en-us/2.0.3/user_doc/guide/project/workflow-instance.md
+++ b/docs/en-us/2.0.3/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.5/user_doc/guide/project/task-instance.md b/docs/en-us/2.0.5/user_doc/guide/project/task-instance.md
index 6d02cdc..49280f5 100644
--- a/docs/en-us/2.0.5/user_doc/guide/project/task-instance.md
+++ b/docs/en-us/2.0.5/user_doc/guide/project/task-instance.md
@@ -6,7 +6,7 @@
<img src="/img/task-list-en.png" width="80%" />
</p>
-- <span id=taskLog>View log：</span>Click the "view log" button in the operation column to view the log of task execution.
+- View log：Click the "view log" button in the operation column to view the log of task execution.
<p align="center">
<img src="/img/task-log2-en.png" width="80%" />
</p>
diff --git a/docs/en-us/2.0.5/user_doc/guide/project/workflow-definition.md b/docs/en-us/2.0.5/user_doc/guide/project/workflow-definition.md
index ddb9d2f..590d3e7 100644
--- a/docs/en-us/2.0.5/user_doc/guide/project/workflow-definition.md
+++ b/docs/en-us/2.0.5/user_doc/guide/project/workflow-definition.md
@@ -1,6 +1,6 @@
# Workflow definition
-## <span id=creatDag> Create workflow definition</span>
+## Create workflow definition
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, and click the "Create Workflow" button to enter the **workflow DAG edit** page, as shown in the following figure:
<p align="center">
@@ -17,7 +17,7 @@
3. Select "Task Priority": When the number of worker threads is insufficient, high-level tasks will be executed first in the execution queue, and tasks with the same priority will be executed in the order of first in, first out;
4. Timeout alarm (optional): Check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will be sent and the task timeout fails;
5. Resources (optional). Resource files are files created or uploaded on the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.
- **Increase the order of task execution:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 are executed in parallel, When task 1 finished executing, tasks 2 and 3 will be executed simultaneously.
@@ -31,11 +31,11 @@
<img src="/img/dag7.png" width="80%" />
</p>
-- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [ Custom parameters](#UserDefinedParameters)), click the "Add" button, and the workflow definition is created successfully.
+- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" pop-up box will pop up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [global parameters](../parameter/global.md)), click the "Add" button, and the workflow definition is created successfully.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
## Workflow definition operation function
@@ -46,11 +46,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The operation functions of the workflow definition list are as follows:
-- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag).
+- **Edit:** Only "offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#create-workflow-definition).
- **Online:** When the workflow status is "Offline", used to online workflow. Only the workflow in the "Online" state can run, but cannot be edited.
- **Offline:** When the workflow status is "Online", used to offline workflow. Only the workflow in the "Offline" state can be edited, but not run.
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps.
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#run-the-workflow) for the operation steps.
+- **Timing:** Timing can only be set in online workflows, and the system automatically schedules the workflow to run on a regular basis. The status after creating a timing is "offline", and the timing must be online on the timing management page to take effect. See [2.3.4 Workflow Timing](#workflow-timing) for timing operation steps.
- **Timing Management:** The timing management page can be edited, online/offline, and deleted.
- **Delete:** Delete the workflow definition.
- **Download:** Download workflow definition to local.
@@ -59,7 +59,7 @@ The operation functions of the workflow definition list are as follows:
<img src="/img/tree_en.png" width="80%" />
</p>
-## <span id=runWorkflow>Run the workflow</span>
+## Run the workflow
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button <img src="/img/online.png" width="35"/>，Go online workflow.
<p align="center">
@@ -70,7 +70,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
- <span id=runParamers>Description of workflow operating parameters:</span>
+ Description of workflow operating parameters:
* Failure strategy: When a task node fails to execute, other parallel task nodes need to execute the strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks being executed, and terminate the entire process.
* Notification strategy: When the process is over, the process execution information notification email is sent according to the process status, including any status is not sent, successful sent, failed sent, successful or failed sent.
@@ -91,7 +91,7 @@ The operation functions of the workflow definition list are as follows:
> Parallel mode: The tasks from May 1 to may 10 are executed simultaneously, and 10 process instances are generated on the process instance page.
-## <span id=creatTiming>Workflow timing</span>
+## Workflow timing
- Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, go online the workflow, click the "timing" button <img src="/img/timing.png" width="35"/> ,The timing parameter setting dialog box pops up, as shown in the figure below:
<p align="center">
@@ -102,7 +102,7 @@ The operation functions of the workflow definition list are as follows:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.
- Click the "Create" button to create the timing successfully. At this time, the timing status is "**Offline**" and the timing needs to be **Online** to take effect.
- Timing online: Click the "timing management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow takes effect regularly.
<p align="center">
diff --git a/docs/en-us/2.0.5/user_doc/guide/project/workflow-instance.md b/docs/en-us/2.0.5/user_doc/guide/project/workflow-instance.md
index ac65ebe..4a8c909 100644
--- a/docs/en-us/2.0.5/user_doc/guide/project/workflow-instance.md
+++ b/docs/en-us/2.0.5/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](#taskLog)。
+- Click "View Log", a log pop-up box will pop up, as shown in the figure below, the task log can also be viewed on the task instance page, refer to [Task View Log](./task-instance.md)。
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/en-us/dev/user_doc/guide/project/task-instance.md b/docs/en-us/dev/user_doc/guide/project/task-instance.md
index 5102b23..bafa588 100644
--- a/docs/en-us/dev/user_doc/guide/project/task-instance.md
+++ b/docs/en-us/dev/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list-en.png" width="80%" />
</p>
-- <span id=taskLog>View log：</span>Click the "view log" button in the operation column to view task execution log.
+- View log：Click the "view log" button in the operation column to view task execution log.
<p align="center">
<img src="/img/task-log2-en.png" width="80%" />
</p>
diff --git a/docs/en-us/dev/user_doc/guide/project/workflow-definition.md b/docs/en-us/dev/user_doc/guide/project/workflow-definition.md
index a8de0f6..400c17e 100644
--- a/docs/en-us/dev/user_doc/guide/project/workflow-definition.md
+++ b/docs/en-us/dev/user_doc/guide/project/workflow-definition.md
@@ -1,6 +1,6 @@
# Workflow Definition
-## <span id=creatDag> Create Workflow Definition</span>
+## Create workflow definition
- Click Project Management -> Workflow -> Workflow Definition, enter the workflow definition page, and click the "Create Workflow" button to enter the **workflow DAG edit** page, as shown in the following figure:
<p align="center">
@@ -17,7 +17,7 @@
3. Select "Task Priority": when the number of worker threads is insufficient, high priority tasks will execute first in the execution queue, and tasks with the same priority will execute in the order of first in, first out;
4. Timeout alarm (optional): check the timeout alarm, timeout failure, and fill in the "timeout period". When the task execution time exceeds **timeout period**, an alert email will send and the task timeout fails;
5. Resources (optional). Resources are files create or upload in the Resource Center -> File Management page. For example, the file name is `test.sh`, and the command to call the resource in the script is `sh test.sh`;
-6. Custom parameters (optional), refer to [Custom Parameters](#UserDefinedParameters);
+6. Customize parameters (optional);
7. Click the "Confirm Add" button to save the task settings.
- **Set dependencies between tasks:** Click the icon in the upper right corner <img src="/img/line.png" width="35"/> to connect the task; as shown in the figure below, task 2 and task 3 execute in parallel, When task 1 finished execution, tasks 2 and 3 will execute simultaneously.
@@ -31,11 +31,11 @@
<img src="/img/dag7.png" width="80%" />
</p>
-- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" window pops up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [Custom parameters](#UserDefinedParameters)), click the "Add" button to finish workflow definition creation.
+- **Save workflow definition:** Click the "Save" button, and the "Set DAG chart name" window pops up, as shown in the figure below. Enter the workflow definition name, workflow definition description, and set global parameters (optional, refer to [global parameters](../parameter/global.md)), click the "Add" button to finish workflow definition creation.
<p align="center">
<img src="/img/dag8.png" width="80%" />
</p>
-> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers).
+> For other types of tasks, please refer to [Task Node Type and Parameter Settings](#TaskParamers). <!-- markdown-link-check-disable-line -->
## Workflow Definition Operation Function
@@ -46,11 +46,11 @@ Click Project Management -> Workflow -> Workflow Definition to enter the workflo
</p>
The following are the operation functions of the workflow definition list:
-- **Edit:** Only "Offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag)
+- **Edit:** Only "Offline" workflow definitions can be edited. Workflow DAG editing is the same as [Create Workflow Definition](#creatDag) <!-- markdown-link-check-disable-line -->
- **Online:** When the workflow status is "Offline", used to make workflow online. Only the workflow in the "Online" state can run, but cannot edit
- **Offline:** When the workflow status is "Online", used to make workflow offline. Only the workflow in the "Offline" state can be edited, but cannot run
-- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#runWorkflow) for the operation steps
-- **Timing:** Timing can only set to online workflows, and the system automatically schedules to run the workflow on time. The status after creating a timing setting is "offline", and the timing must set online on the timing management page to make effect. See [2.3.4 Workflow Timing](#creatTiming) for timing operation steps
+- **Run:** Only workflow in the online state can run. See [2.3.3 Run Workflow](#run-the-workflow) for the operation steps.
+- **Timing:** Timing can only set to online workflows, and the system automatically schedules to run the workflow on time. The status after creating a timing setting is "offline", and the timing must set online on the timing management page to make effect. See [2.3.4 Workflow Timing](#workflow-timing) for timing operation steps
- **Timing Management:** The timing management page can edit, online or offline and delete timing
- **Delete:** Delete the workflow definition
- **Download:** Download workflow definition to local
@@ -59,7 +59,7 @@ The following are the operation functions of the workflow definition list:
<img src="/img/tree_en.png" width="80%" />
</p>
-## <span id=runWorkflow>Run the Workflow</span>
+## Run the Workflow
- Click Project Management -> Workflow -> Workflow Definition to enter the workflow definition page, as shown in the figure below, click the "Go Online" button <img src="/img/online.png" width="35"/>to make workflow online.
<p align="center">
@@ -70,7 +70,7 @@ The following are the operation functions of the workflow definition list:
<p align="center">
<img src="/img/run_work_en.png" width="80%" />
</p>
- <span id=runParamers>Description of workflow operating parameters:</span>
+ Description of workflow operating parameters:
* Failure strategy: When a task node fails to execute, other parallel task nodes need to execute this strategy. "Continue" means: after a certain task fails, other task nodes execute normally; "End" means: terminate all tasks execution, and terminate the entire process
* Notification strategy: When the process is over, send the process execution result notification email according to the process status, options including no send, send if sucess, send of failure, send whatever result
@@ -91,7 +91,7 @@ The following are the operation functions of the workflow definition list:
> Parallel mode: The tasks from 1st May to 10th May execute simultaneously, and the process instance page generates 10 process instances;
-## <span id=creatTiming>Workflow Timing</span>
+## Workflow Timing
- Create timing: Click Project Management->Workflow->Workflow Definition, enter the workflow definition page, make the workflow online, click the "timing" button <img src="/img/timing.png" width="35"/> , the timing parameter setting dialog box pops up, as shown in the figure below:
<p align="center">
@@ -102,7 +102,7 @@ The following are the operation functions of the workflow definition list:
<p align="center">
<img src="/img/timer-en.png" width="80%" />
</p>
-- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as [workflow running parameters](#runParamers).
+- Failure strategy, notification strategy, process priority, worker group, notification group, recipient, and CC are the same as workflow running parameters.
- Click the "Create" button to create the timing. Now the timing status is "**Offline**" and the timing needs to be **Online** to make effect.
- Timing online: Click the "Timing Management" button <img src="/img/timeManagement.png" width="35"/>, enter the timing management page, click the "online" button, the timing status will change to "online", as shown in the below figure, the workflow makes effect regularly.
<p align="center">
diff --git a/docs/en-us/dev/user_doc/guide/project/workflow-instance.md b/docs/en-us/dev/user_doc/guide/project/workflow-instance.md
index 2f2e0b0..51670a3 100644
--- a/docs/en-us/dev/user_doc/guide/project/workflow-instance.md
+++ b/docs/en-us/dev/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog-en.png" width="80%" />
</p>
-- Click "View Log", a log window pops up, as shown in the figure below, you can also view the task log on the task instance page, refer to [Task View Log](#taskLog)
+- Click "View Log", a log window pops up, as shown in the figure below, you can also view the task log on the task instance page, refer to [Task View Log](./task-instance.md)
<p align="center">
<img src="/img/task-log-en.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.2.0/user_doc/system-manual.md b/docs/zh-cn/1.2.0/user_doc/system-manual.md
index da72202..46e992e 100644
--- a/docs/zh-cn/1.2.0/user_doc/system-manual.md
+++ b/docs/zh-cn/1.2.0/user_doc/system-manual.md
@@ -47,6 +47,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+ <!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -61,22 +62,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+ <!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时 后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -124,7 +126,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -148,7 +150,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.2.1/user_doc/system-manual.md b/docs/zh-cn/1.2.1/user_doc/system-manual.md
index e4e659f..409216f 100644
--- a/docs/zh-cn/1.2.1/user_doc/system-manual.md
+++ b/docs/zh-cn/1.2.1/user_doc/system-manual.md
@@ -47,6 +47,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+ <!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -61,22 +62,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -124,7 +126,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -148,7 +150,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.1/user_doc/system-manual.md b/docs/zh-cn/1.3.1/user_doc/system-manual.md
index 02b5503..2971c3f 100644
--- a/docs/zh-cn/1.3.1/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.1/user_doc/system-manual.md
@@ -47,6 +47,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+<!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -61,22 +62,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -124,7 +126,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -148,7 +150,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.2/user_doc/system-manual.md b/docs/zh-cn/1.3.2/user_doc/system-manual.md
index c017a05..6108911 100644
--- a/docs/zh-cn/1.3.2/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.2/user_doc/system-manual.md
@@ -45,6 +45,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+<!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -59,22 +60,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -122,7 +124,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -146,7 +148,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.3/user_doc/system-manual.md b/docs/zh-cn/1.3.3/user_doc/system-manual.md
index 811444d..76e0f24 100644
--- a/docs/zh-cn/1.3.3/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.3/user_doc/system-manual.md
@@ -47,6 +47,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+<!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -61,22 +62,23 @@
<img src="/img/dag3.png" width="100%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="100%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="100%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -124,7 +126,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="100%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -148,7 +150,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="100%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="100%" />
</p>
diff --git a/docs/zh-cn/1.3.4/user_doc/system-manual.md b/docs/zh-cn/1.3.4/user_doc/system-manual.md
index 7064450..e263c75 100644
--- a/docs/zh-cn/1.3.4/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.4/user_doc/system-manual.md
@@ -45,6 +45,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+ <!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -59,22 +60,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+ <!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -123,7 +125,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -147,7 +149,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.5/user_doc/kubernetes-deployment.md b/docs/zh-cn/1.3.5/user_doc/kubernetes-deployment.md
index 80d66d1..063be54 100644
--- a/docs/zh-cn/1.3.5/user_doc/kubernetes-deployment.md
+++ b/docs/zh-cn/1.3.5/user_doc/kubernetes-deployment.md
@@ -28,7 +28,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[配置](#configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[配置](#configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
diff --git a/docs/zh-cn/1.3.5/user_doc/system-manual.md b/docs/zh-cn/1.3.5/user_doc/system-manual.md
index 760afe9..592b5e2 100644
--- a/docs/zh-cn/1.3.5/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.5/user_doc/system-manual.md
@@ -45,6 +45,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+<!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -59,22 +60,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -124,7 +126,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -148,7 +150,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.6/user_doc/docker-deployment.md b/docs/zh-cn/1.3.6/user_doc/docker-deployment.md
index b0dab2c..974e9ca 100644
--- a/docs/zh-cn/1.3.6/user_doc/docker-deployment.md
+++ b/docs/zh-cn/1.3.6/user_doc/docker-deployment.md
@@ -161,7 +161,7 @@ apache/dolphinscheduler:1.3.6 alert-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/1.3.6/user_doc/kubernetes-deployment.md b/docs/zh-cn/1.3.6/user_doc/kubernetes-deployment.md
index 50c8b00..e417671 100644
--- a/docs/zh-cn/1.3.6/user_doc/kubernetes-deployment.md
+++ b/docs/zh-cn/1.3.6/user_doc/kubernetes-deployment.md
@@ -28,7 +28,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -85,7 +85,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/1.3.6/user_doc/system-manual.md b/docs/zh-cn/1.3.6/user_doc/system-manual.md
index 64a885f..a3b4b9d 100644
--- a/docs/zh-cn/1.3.6/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.6/user_doc/system-manual.md
@@ -45,6 +45,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
+<!-- markdown-link-check-disable-next-line -->
1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
@@ -59,22 +60,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -123,7 +125,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -147,7 +149,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.8/user_doc/docker-deployment.md b/docs/zh-cn/1.3.8/user_doc/docker-deployment.md
index e02ab21..db359aa 100644
--- a/docs/zh-cn/1.3.8/user_doc/docker-deployment.md
+++ b/docs/zh-cn/1.3.8/user_doc/docker-deployment.md
@@ -161,7 +161,7 @@ apache/dolphinscheduler:1.3.8 alert-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/1.3.8/user_doc/kubernetes-deployment.md b/docs/zh-cn/1.3.8/user_doc/kubernetes-deployment.md
index 7edf1a1..a5cd1fa 100644
--- a/docs/zh-cn/1.3.8/user_doc/kubernetes-deployment.md
+++ b/docs/zh-cn/1.3.8/user_doc/kubernetes-deployment.md
@@ -28,7 +28,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -85,7 +85,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/1.3.8/user_doc/system-manual.md b/docs/zh-cn/1.3.8/user_doc/system-manual.md
index 5422c74..288679f 100644
--- a/docs/zh-cn/1.3.8/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.8/user_doc/system-manual.md
@@ -47,7 +47,9 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+
+<!-- markdown-link-check-disable-next-line -->
+1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -61,22 +63,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
+<!-- markdown-link-check-disable-next-line -->
- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -125,7 +128,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -149,7 +152,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/1.3.9/user_doc/docker-deployment.md b/docs/zh-cn/1.3.9/user_doc/docker-deployment.md
index 1b40718..6e3235a 100644
--- a/docs/zh-cn/1.3.9/user_doc/docker-deployment.md
+++ b/docs/zh-cn/1.3.9/user_doc/docker-deployment.md
@@ -161,7 +161,7 @@ apache/dolphinscheduler:1.3.9 alert-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/1.3.9/user_doc/kubernetes-deployment.md b/docs/zh-cn/1.3.9/user_doc/kubernetes-deployment.md
index 7edf1a1..a5cd1fa 100644
--- a/docs/zh-cn/1.3.9/user_doc/kubernetes-deployment.md
+++ b/docs/zh-cn/1.3.9/user_doc/kubernetes-deployment.md
@@ -28,7 +28,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -85,7 +85,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/1.3.9/user_doc/system-manual.md b/docs/zh-cn/1.3.9/user_doc/system-manual.md
index 64a885f..e22628e 100644
--- a/docs/zh-cn/1.3.9/user_doc/system-manual.md
+++ b/docs/zh-cn/1.3.9/user_doc/system-manual.md
@@ -45,7 +45,8 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+<!-- markdown-link-check-disable-next-line -->
+ 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)； <!-- markdown-link-check-disable-line -->
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -59,22 +60,23 @@
<img src="/img/dag3.png" width="80%" />
</p>
- - **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+<!-- markdown-link-check-disable-next-line -->
+ - **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
#### 2.3.2 工作流定义操作功能
点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示:
<p align="center">
<img src="/img/work_list.png" width="80%" />
</p>
工作流定义列表的操作功能如下：
- - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+ - **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。 <!-- markdown-link-check-disable-line -->
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
- - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
- - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+ - **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow) <!-- markdown-link-check-disable-line -->
+ - **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -123,7 +125,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
- - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+ - 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
@@ -147,7 +149,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
- - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+ - 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。 <!-- markdown-link-check-disable-line -->
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/2.0.0/user_doc/guide/installation/docker.md b/docs/zh-cn/2.0.0/user_doc/guide/installation/docker.md
index 8c895cc..757171a 100644
--- a/docs/zh-cn/2.0.0/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/2.0.0/user_doc/guide/installation/docker.md
@@ -161,7 +161,7 @@ apache/dolphinscheduler:2.0.0 alert-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/2.0.0/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/2.0.0/user_doc/guide/installation/kubernetes.md
index ba3e051..a871a69 100644
--- a/docs/zh-cn/2.0.0/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/2.0.0/user_doc/guide/installation/kubernetes.md
@@ -33,7 +33,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -90,7 +90,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/2.0.0/user_doc/guide/project/task-instance.md b/docs/zh-cn/2.0.0/user_doc/guide/project/task-instance.md
index 3f0a276..8a9b5ad 100644
--- a/docs/zh-cn/2.0.0/user_doc/guide/project/task-instance.md
+++ b/docs/zh-cn/2.0.0/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list.png" width="80%" />
</p>
-- <span id=taskLog>查看日志：</span>点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
+- 查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
<p align="center">
<img src="/img/task-log2.png" width="80%" />
</p>
\ No newline at end of file
diff --git a/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-definition.md b/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-definition.md
index e69261f..d46c87a 100644
--- a/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-definition.md
+++ b/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-definition.md
@@ -16,7 +16,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+ 1. 自定义参数（非必填）；
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -30,11 +30,11 @@
<img src="/img/dag3.png" width="80%" />
</p>
-- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[全局参数](../parameter/global.md)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
## 工作流定义操作功能
@@ -44,11 +44,11 @@
</p>
工作流定义列表的操作功能如下：
-- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同创建工作流定义。
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
-- **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
-- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+- **运行：** 只有上线的工作流能运行。运行操作步骤见运行工作流
+- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。 <!-- markdown-link-check-disable-line -->
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -57,7 +57,7 @@
<img src="/img/tree.png" width="80%" />
</p>
-## <span id=runWorkflow>运行工作流</span>
+## 运行工作流
- 点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示，点击"上线"按钮<img src="/img/online.png" width="35"/>，上线工作流。
<p align="center">
@@ -68,7 +68,7 @@
<p align="center">
<img src="/img/run-work.png" width="80%" />
</p>
- <span id=runParamers>工作流运行参数说明：</span>
+ 工作流运行参数说明：
* 失败策略：当某一个任务节点执行失败时，其他并行的任务节点需要执行的策略。”继续“表示：某一任务失败后，其他任务节点正常执行；”结束“表示：终止所有正在执行的任务，并终止整个流程。
* 通知策略：当流程结束，根据流程状态发送流程执行信息通知邮件，包含任何状态都不发，成功发，失败发，成功或失败都发。
@@ -99,7 +99,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
-- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同工作流运行参数。
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
diff --git a/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-instance.md b/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-instance.md
index 54625d4..e8f2f76 100644
--- a/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-instance.md
+++ b/docs/zh-cn/2.0.0/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
-- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](./task-instance.md)。
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/2.0.1/user_doc/guide/installation/docker.md b/docs/zh-cn/2.0.1/user_doc/guide/installation/docker.md
index fbea76e..425d72c 100644
--- a/docs/zh-cn/2.0.1/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/2.0.1/user_doc/guide/installation/docker.md
@@ -161,7 +161,7 @@ apache/dolphinscheduler:2.0.1 alert-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/2.0.1/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/2.0.1/user_doc/guide/installation/kubernetes.md
index 37f38e9..671857f 100644
--- a/docs/zh-cn/2.0.1/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/2.0.1/user_doc/guide/installation/kubernetes.md
@@ -33,7 +33,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -90,7 +90,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/2.0.1/user_doc/guide/project/task-instance.md b/docs/zh-cn/2.0.1/user_doc/guide/project/task-instance.md
index 3f0a276..8a9b5ad 100644
--- a/docs/zh-cn/2.0.1/user_doc/guide/project/task-instance.md
+++ b/docs/zh-cn/2.0.1/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list.png" width="80%" />
</p>
-- <span id=taskLog>查看日志：</span>点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
+- 查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
<p align="center">
<img src="/img/task-log2.png" width="80%" />
</p>
\ No newline at end of file
diff --git a/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-definition.md b/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-definition.md
index e69261f..2f3de05 100644
--- a/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-definition.md
+++ b/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-definition.md
@@ -16,7 +16,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+ 1. 自定义参数（非必填）；
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -30,11 +30,11 @@
<img src="/img/dag3.png" width="80%" />
</p>
-- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[全局参数](../parameter/global.md)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
## 工作流定义操作功能
@@ -44,11 +44,11 @@
</p>
工作流定义列表的操作功能如下：
-- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同创建工作流定义。
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
-- **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
-- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+- **运行：** 只有上线的工作流能运行。运行操作步骤见运行工作流
+- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见工作流定时。
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -57,7 +57,7 @@
<img src="/img/tree.png" width="80%" />
</p>
-## <span id=runWorkflow>运行工作流</span>
+## 运行工作流
- 点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示，点击"上线"按钮<img src="/img/online.png" width="35"/>，上线工作流。
<p align="center">
@@ -68,7 +68,7 @@
<p align="center">
<img src="/img/run-work.png" width="80%" />
</p>
- <span id=runParamers>工作流运行参数说明：</span>
+ 工作流运行参数说明：
* 失败策略：当某一个任务节点执行失败时，其他并行的任务节点需要执行的策略。”继续“表示：某一任务失败后，其他任务节点正常执行；”结束“表示：终止所有正在执行的任务，并终止整个流程。
* 通知策略：当流程结束，根据流程状态发送流程执行信息通知邮件，包含任何状态都不发，成功发，失败发，成功或失败都发。
@@ -88,7 +88,7 @@
> 并行模式：同时执行5月1号到5月10号的任务，同时在流程实例页面生成十条流程实例。
-## <span id=creatTiming>工作流定时</span>
+## 工作流定时
- 创建定时：点击项目管理->工作流->工作流定义，进入工作流定义页面，上线工作流，点击"定时"按钮<img src="/img/timing.png" width="35"/>,弹出定时参数设置弹框，如下图所示：
<p align="center">
@@ -99,7 +99,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
-- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同工作流运行参数。
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
diff --git a/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-instance.md b/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-instance.md
index 54625d4..e8f2f76 100644
--- a/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-instance.md
+++ b/docs/zh-cn/2.0.1/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
-- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](./task-instance.md)。
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/2.0.2/user_doc/guide/installation/docker.md b/docs/zh-cn/2.0.2/user_doc/guide/installation/docker.md
index 202ec18..53952de 100644
--- a/docs/zh-cn/2.0.2/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/2.0.2/user_doc/guide/installation/docker.md
@@ -171,7 +171,7 @@ apache/dolphinscheduler:2.0.2 python-gateway-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/2.0.2/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/2.0.2/user_doc/guide/installation/kubernetes.md
index a15f8a7..d83ee66 100644
--- a/docs/zh-cn/2.0.2/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/2.0.2/user_doc/guide/installation/kubernetes.md
@@ -33,7 +33,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -90,7 +90,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/2.0.2/user_doc/guide/project/task-instance.md b/docs/zh-cn/2.0.2/user_doc/guide/project/task-instance.md
index 3f0a276..8a9b5ad 100644
--- a/docs/zh-cn/2.0.2/user_doc/guide/project/task-instance.md
+++ b/docs/zh-cn/2.0.2/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list.png" width="80%" />
</p>
-- <span id=taskLog>查看日志：</span>点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
+- 查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
<p align="center">
<img src="/img/task-log2.png" width="80%" />
</p>
\ No newline at end of file
diff --git a/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-definition.md b/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-definition.md
index e69261f..67da3a1 100644
--- a/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-definition.md
+++ b/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-definition.md
@@ -16,7 +16,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+ 1. 自定义参数（非必填）；
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -30,11 +30,11 @@
<img src="/img/dag3.png" width="80%" />
</p>
-- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[全局参数](../parameter/global.md)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
## 工作流定义操作功能
@@ -44,11 +44,11 @@
</p>
工作流定义列表的操作功能如下：
-- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同创建工作流定义。
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
-- **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
-- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+- **运行：** 只有上线的工作流能运行。运行操作步骤见运行工作流
+- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见工作流定时
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -57,7 +57,7 @@
<img src="/img/tree.png" width="80%" />
</p>
-## <span id=runWorkflow>运行工作流</span>
+## 运行工作流
- 点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示，点击"上线"按钮<img src="/img/online.png" width="35"/>，上线工作流。
<p align="center">
@@ -68,7 +68,7 @@
<p align="center">
<img src="/img/run-work.png" width="80%" />
</p>
- <span id=runParamers>工作流运行参数说明：</span>
+ 工作流运行参数说明：
* 失败策略：当某一个任务节点执行失败时，其他并行的任务节点需要执行的策略。”继续“表示：某一任务失败后，其他任务节点正常执行；”结束“表示：终止所有正在执行的任务，并终止整个流程。
* 通知策略：当流程结束，根据流程状态发送流程执行信息通知邮件，包含任何状态都不发，成功发，失败发，成功或失败都发。
@@ -99,7 +99,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
-- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同工作流运行参数。
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
diff --git a/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-instance.md b/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-instance.md
index 54625d4..e8f2f76 100644
--- a/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-instance.md
+++ b/docs/zh-cn/2.0.2/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
-- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](./task-instance.md)。
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/2.0.3/user_doc/guide/installation/docker.md b/docs/zh-cn/2.0.3/user_doc/guide/installation/docker.md
index f761f76..c9da3a8 100644
--- a/docs/zh-cn/2.0.3/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/2.0.3/user_doc/guide/installation/docker.md
@@ -171,7 +171,7 @@ apache/dolphinscheduler:2.0.3 python-gateway-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/2.0.3/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/2.0.3/user_doc/guide/installation/kubernetes.md
index 47301cc..5bcc582 100644
--- a/docs/zh-cn/2.0.3/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/2.0.3/user_doc/guide/installation/kubernetes.md
@@ -33,7 +33,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -90,7 +90,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/2.0.3/user_doc/guide/project/task-instance.md b/docs/zh-cn/2.0.3/user_doc/guide/project/task-instance.md
index 3f0a276..8a9b5ad 100644
--- a/docs/zh-cn/2.0.3/user_doc/guide/project/task-instance.md
+++ b/docs/zh-cn/2.0.3/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list.png" width="80%" />
</p>
-- <span id=taskLog>查看日志：</span>点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
+- 查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
<p align="center">
<img src="/img/task-log2.png" width="80%" />
</p>
\ No newline at end of file
diff --git a/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-definition.md b/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-definition.md
index e69261f..67da3a1 100644
--- a/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-definition.md
+++ b/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-definition.md
@@ -16,7 +16,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+ 1. 自定义参数（非必填）；
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -30,11 +30,11 @@
<img src="/img/dag3.png" width="80%" />
</p>
-- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[全局参数](../parameter/global.md)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
## 工作流定义操作功能
@@ -44,11 +44,11 @@
</p>
工作流定义列表的操作功能如下：
-- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同创建工作流定义。
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
-- **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
-- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+- **运行：** 只有上线的工作流能运行。运行操作步骤见运行工作流
+- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见工作流定时
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -57,7 +57,7 @@
<img src="/img/tree.png" width="80%" />
</p>
-## <span id=runWorkflow>运行工作流</span>
+## 运行工作流
- 点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示，点击"上线"按钮<img src="/img/online.png" width="35"/>，上线工作流。
<p align="center">
@@ -68,7 +68,7 @@
<p align="center">
<img src="/img/run-work.png" width="80%" />
</p>
- <span id=runParamers>工作流运行参数说明：</span>
+ 工作流运行参数说明：
* 失败策略：当某一个任务节点执行失败时，其他并行的任务节点需要执行的策略。”继续“表示：某一任务失败后，其他任务节点正常执行；”结束“表示：终止所有正在执行的任务，并终止整个流程。
* 通知策略：当流程结束，根据流程状态发送流程执行信息通知邮件，包含任何状态都不发，成功发，失败发，成功或失败都发。
@@ -99,7 +99,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
-- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同工作流运行参数。
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
diff --git a/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-instance.md b/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-instance.md
index 54625d4..e8f2f76 100644
--- a/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-instance.md
+++ b/docs/zh-cn/2.0.3/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
-- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](./task-instance.md)。
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/2.0.5/user_doc/guide/installation/docker.md b/docs/zh-cn/2.0.5/user_doc/guide/installation/docker.md
index 074e60d..bd6da65 100644
--- a/docs/zh-cn/2.0.5/user_doc/guide/installation/docker.md
+++ b/docs/zh-cn/2.0.5/user_doc/guide/installation/docker.md
@@ -171,7 +171,7 @@ apache/dolphinscheduler:2.0.5 python-gateway-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置
diff --git a/docs/zh-cn/2.0.5/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/2.0.5/user_doc/guide/installation/kubernetes.md
index ea005a8..aed07fd 100644
--- a/docs/zh-cn/2.0.5/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/2.0.5/user_doc/guide/installation/kubernetes.md
@@ -33,7 +33,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -90,7 +90,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/2.0.5/user_doc/guide/project/task-instance.md b/docs/zh-cn/2.0.5/user_doc/guide/project/task-instance.md
index 3f0a276..8a9b5ad 100644
--- a/docs/zh-cn/2.0.5/user_doc/guide/project/task-instance.md
+++ b/docs/zh-cn/2.0.5/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list.png" width="80%" />
</p>
-- <span id=taskLog>查看日志：</span>点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
+- 查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
<p align="center">
<img src="/img/task-log2.png" width="80%" />
</p>
\ No newline at end of file
diff --git a/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-definition.md b/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-definition.md
index e69261f..a4afb70 100644
--- a/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-definition.md
+++ b/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-definition.md
@@ -16,7 +16,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+ 1. 自定义参数（非必填）；
1. 点击"确认添加"按钮，保存任务设置。
- **增加任务执行的先后顺序：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -30,11 +30,11 @@
<img src="/img/dag3.png" width="80%" />
</p>
-- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[全局参数](../parameter/global.md)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
## 工作流定义操作功能
@@ -44,11 +44,11 @@
</p>
工作流定义列表的操作功能如下：
-- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同创建工作流定义。
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
-- **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
-- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+- **运行：** 只有上线的工作流能运行。运行操作步骤见运行工作流
+- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见工作流定时
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -57,7 +57,7 @@
<img src="/img/tree.png" width="80%" />
</p>
-## <span id=runWorkflow>运行工作流</span>
+## 运行工作流
- 点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示，点击"上线"按钮<img src="/img/online.png" width="35"/>，上线工作流。
<p align="center">
@@ -99,7 +99,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
-- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。 <!-- markdown-link-check-disable-line -->
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
diff --git a/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-instance.md b/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-instance.md
index 54625d4..e8f2f76 100644
--- a/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-instance.md
+++ b/docs/zh-cn/2.0.5/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
-- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](./task-instance.md)。
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md b/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
index e3b0fb5..5b66816 100644
--- a/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
+++ b/docs/zh-cn/dev/user_doc/guide/installation/kubernetes.md
@@ -33,7 +33,7 @@ $ helm install dolphinscheduler . -n test
> **提示**: 如果名为 `test` 的命名空间被使用, 选项参数 `-n test` 需要添加到 `helm` 和 `kubectl` 命令中
-这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数
+这些命令以默认配置在 Kubernetes 集群上部署 DolphinScheduler，[附录-配置](#appendix-configuration)部分列出了可以在安装过程中配置的参数 <!-- markdown-link-check-disable-line -->
> **提示**: 列出所有已发布的版本，使用 `helm list`
@@ -90,7 +90,7 @@ $ kubectl delete pvc -l app.kubernetes.io/instance=dolphinscheduler
## 配置
-配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值
+配置文件为 `values.yaml`，[附录-配置](#appendix-configuration) 表格列出了 DolphinScheduler 的可配置参数及其默认值 <!-- markdown-link-check-disable-line -->
## 支持矩阵
diff --git a/docs/zh-cn/dev/user_doc/guide/project/task-instance.md b/docs/zh-cn/dev/user_doc/guide/project/task-instance.md
index 3f0a276..8a9b5ad 100644
--- a/docs/zh-cn/dev/user_doc/guide/project/task-instance.md
+++ b/docs/zh-cn/dev/user_doc/guide/project/task-instance.md
@@ -5,7 +5,7 @@
<img src="/img/task-list.png" width="80%" />
</p>
-- <span id=taskLog>查看日志：</span>点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
+- 查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。
<p align="center">
<img src="/img/task-log2.png" width="80%" />
</p>
\ No newline at end of file
diff --git a/docs/zh-cn/dev/user_doc/guide/project/workflow-definition.md b/docs/zh-cn/dev/user_doc/guide/project/workflow-definition.md
index 7b775a1..643d166 100644
--- a/docs/zh-cn/dev/user_doc/guide/project/workflow-definition.md
+++ b/docs/zh-cn/dev/user_doc/guide/project/workflow-definition.md
@@ -14,7 +14,7 @@
1. 选择“任务优先级”：当worker线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；
1. 超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过**超时时长**，会发送告警邮件并且任务超时失败；
1. 资源（非必选）。资源文件是资源中心->文件管理页面创建或上传的文件，如文件名为`test.sh`，脚本中调用资源命令为`sh test.sh`；
- 1. 自定义参数（非必填），参考[自定义参数](#UserDefinedParameters)；
+ 1. 自定义参数（非必填）；
1. 点击"确认添加"按钮，保存任务设置。
- **配置任务之间的依赖关系：** 点击右上角图标<img src="/img/line.png" width="35"/>连接任务；如下图所示，任务2和任务3并行执行，当任务1执行完，任务2、3会同时执行。
@@ -28,11 +28,11 @@
<img src="/img/dag3.png" width="80%" />
</p>
-- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[自定义参数](#UserDefinedParameters)），点击"添加"按钮，工作流定义创建成功。
+- **保存工作流定义：** 点击”保存“按钮，弹出"设置DAG图名称"弹框，如下图所示，输入工作流定义名称，工作流定义描述，设置全局参数（选填，参考[全局参数](../parameter/global.md)），点击"添加"按钮，工作流定义创建成功。
<p align="center">
<img src="/img/dag4.png" width="80%" />
</p>
- > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。
+ > 其他类型任务，请参考 [任务节点类型和参数设置](#TaskParamers)。 <!-- markdown-link-check-disable-line -->
## 工作流定义操作功能
@@ -42,11 +42,11 @@
</p>
工作流定义列表的操作功能如下：
-- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同[创建工作流定义](#creatDag)。
+- **编辑：** 只能编辑"下线"的工作流定义。工作流DAG编辑同创建工作流定义。
- **上线：** 工作流状态为"下线"时，上线工作流，只有"上线"状态的工作流能运行，但不能编辑。
- **下线：** 工作流状态为"上线"时，下线工作流，下线状态的工作流可以编辑，但不能运行。
-- **运行：** 只有上线的工作流能运行。运行操作步骤见[2.3.3 运行工作流](#runWorkflow)
-- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见[2.3.4 工作流定时](#creatTiming)。
+- **运行：** 只有上线的工作流能运行。运行操作步骤见运行工作流
+- **定时：** 只有上线的工作流能设置定时，系统自动定时调度工作流运行。创建定时后的状态为"下线"，需在定时管理页面上线定时才生效。定时操作步骤见工作流定时
- **定时管理：** 定时管理页面可编辑、上线/下线、删除定时。
- **删除：** 删除工作流定义。
- **下载：** 下载工作流定义到本地。
@@ -55,7 +55,7 @@
<img src="/img/tree.png" width="80%" />
</p>
-## <span id=runWorkflow>运行工作流</span>
+## 运行工作流
- 点击项目管理->工作流->工作流定义，进入工作流定义页面，如下图所示，点击"上线"按钮<img src="/img/online.png" width="35"/>，上线工作流。
<p align="center">
@@ -66,7 +66,7 @@
<p align="center">
<img src="/img/run-work.png" width="80%" />
</p>
- <span id=runParamers>工作流运行参数说明：</span>
+ 工作流运行参数说明：
* 失败策略：当某一个任务节点执行失败时，其他并行的任务节点需要执行的策略。”继续“表示：某一任务失败后，其他任务节点正常执行；”结束“表示：终止所有正在执行的任务，并终止整个流程。
* 通知策略：当流程结束，根据流程状态发送流程执行信息通知邮件，包含任何状态都不发，成功发，失败发，成功或失败都发。
@@ -97,7 +97,7 @@
<p align="center">
<img src="/img/time-schedule2.png" width="80%" />
</p>
-- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同[工作流运行参数](#runParamers)。
+- 失败策略、通知策略、流程优先级、Worker分组、通知组、收件人、抄送人同工作流运行参数。
- 点击"创建"按钮，创建定时成功，此时定时状态为"**下线**"，定时需**上线**才生效。
- 定时上线：点击"定时管理"按钮<img src="/img/timeManagement.png" width="35"/>，进入定时管理页面，点击"上线"按钮，定时状态变为"上线"，如下图所示，工作流定时生效。
<p align="center">
diff --git a/docs/zh-cn/dev/user_doc/guide/project/workflow-instance.md b/docs/zh-cn/dev/user_doc/guide/project/workflow-instance.md
index 54625d4..e8f2f76 100644
--- a/docs/zh-cn/dev/user_doc/guide/project/workflow-instance.md
+++ b/docs/zh-cn/dev/user_doc/guide/project/workflow-instance.md
@@ -17,7 +17,7 @@
<p align="center">
<img src="/img/instanceViewLog.png" width="80%" />
</p>
-- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](#taskLog)。
+- 点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考[任务查看日志](./task-instance.md)。
<p align="center">
<img src="/img/task-log.png" width="80%" />
</p>
diff --git a/docs/zh-cn/dev/user_doc/guide/start/docker.md b/docs/zh-cn/dev/user_doc/guide/start/docker.md
index 376944e..c78b283 100644
--- a/docs/zh-cn/dev/user_doc/guide/start/docker.md
+++ b/docs/zh-cn/dev/user_doc/guide/start/docker.md
@@ -160,7 +160,7 @@ apache/dolphinscheduler:1.3.8 alert-server
## 环境变量
-Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值
+Docker 容器通过环境变量进行配置，[附录-环境变量](#appendix-environment-variables) 列出了 DolphinScheduler 的可配置环境变量及其默认值 <!-- markdown-link-check-disable-line -->
特别地，在 Docker Compose 和 Docker Swarm 中，可以通过环境变量配置文件 `config.env.sh` 进行配置