[3.1.1][release] Update version to 3.1.1 before release (#12755)

This commit is contained in:
Kerwin 2022-11-07 19:32:39 +08:00 committed by GitHub
parent 251756f410
commit 0fcbc5e401
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
16 changed files with 273 additions and 266 deletions

View File

@ -16,7 +16,7 @@
# under the License.
#
HUB=apache
TAG=3.1.0
TAG=3.1.1
TZ=Asia/Shanghai
DATABASE=postgresql

View File

@ -35,11 +35,11 @@ type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: 3.1.0
version: 3.1.1
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
appVersion: 3.1.0
appVersion: 3.1.1
dependencies:
- name: postgresql

View File

@ -23,7 +23,7 @@ timezone: "Asia/Shanghai"
image:
registry: "dolphinscheduler.docker.scarf.sh/apache"
tag: "3.1.0"
tag: "3.1.1"
pullPolicy: "IfNotPresent"
pullSecret: ""
master: dolphinscheduler-master

File diff suppressed because it is too large Load Diff

View File

@ -30,9 +30,9 @@ Attention: DolphinScheduler itself does not depend on Hadoop, Hive, Spark, but w
mkdir -p /opt
cd /opt
# decompress
tar -zxvf apache-dolphinscheduler-3.1.0-bin.tar.gz -C /opt
tar -zxvf apache-dolphinscheduler-3.1.1-bin.tar.gz -C /opt
cd /opt
mv apache-dolphinscheduler-3.1.0-bin dolphinscheduler
mv apache-dolphinscheduler-3.1.1-bin dolphinscheduler
```
```markdown

View File

@ -19,7 +19,7 @@ Start DolphinScheduler with standalone-server Docker images is the easiest way t
you can learn DolphinScheduler's concepts and usage, with minimal cost.
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
$ docker run --name dolphinscheduler-standalone-server -p 12345:12345 -p 25333:25333 -d apache/dolphinscheduler-standalone-server:"${DOLPHINSCHEDULER_VERSION}"
```
@ -49,7 +49,7 @@ After complete the configuration, we can get the `docker-compose.yaml` file from
form its source package, and make sure you get the right version. After download the package, you can run the commands as below.
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
$ tar -zxf apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src.tar.gz
# Going to docker-compose's location
# For Mac or Linux users
@ -72,7 +72,7 @@ $ docker-compose --profile all up -d
container when it up. You could start DolphinScheduler server separately if you want to reuse your exists services.
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
# Initialize the database, make sure database <DATABASE> already exists
$ docker run -d --name dolphinscheduler-tools \
-e DATABASE="postgresql" \
@ -133,5 +133,5 @@ and use `admin` and `dolphinscheduler123` as default username and password in th
You can modify some environment variables to change configurations when you are starting servers through Docker. We have
an example in [using exists PostgreSQL ZooKeeper](#using-exists-postgresql-zookeeper) to change database and ZooKeeper configurations,
and you could find all environment variables in [all environment variables](https://github.com/apache/dolphinscheduler/blob/3.1.0/script/env/dolphinscheduler_env.sh) <!-- markdown-link-check-disable-line -->
and you could find all environment variables in [all environment variables](https://github.com/apache/dolphinscheduler/blob/3.1.1/script/env/dolphinscheduler_env.sh) <!-- markdown-link-check-disable-line -->
and change them if you want.

View File

@ -4,6 +4,10 @@
#### Setup instructions, are available for each stable version of Apache DolphinScheduler below:
### Versions: 3.1.1
#### Links [3.1.1 Document](../3.1.1/user_doc/about/introduction.md)
### Versions: 3.1.0
#### Links [3.1.0 Document](../3.1.0/user_doc/about/introduction.md)

View File

@ -30,9 +30,9 @@
mkdir -p /opt
cd /opt
# 解压缩
tar -zxvf apache-dolphinscheduler-3.1.0-bin.tar.gz -C /opt
tar -zxvf apache-dolphinscheduler-3.1.1-bin.tar.gz -C /opt
cd /opt
mv apache-dolphinscheduler-3.1.0-bin dolphinscheduler
mv apache-dolphinscheduler-3.1.1-bin dolphinscheduler
```
```markdown

View File

@ -17,7 +17,7 @@
你可以最快速的体验到 DolphinScheduler 的大部分功能,了解主要和概念和内容。
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
$ docker run --name dolphinscheduler-standalone-server -p 12345:12345 -p 25333:25333 -d apache/dolphinscheduler-standalone-server:"${DOLPHINSCHEDULER_VERSION}"
```
@ -43,7 +43,7 @@ $ docker run --name dolphinscheduler-standalone-server -p 12345:12345 -p 25333:2
源码包对应的值为 "Total Source Code"。当下载完源码后就可以运行命令进行部署了。
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
$ tar -zxf apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src.tar.gz
# Mac Linux 用户
$ cd apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src/deploy/docker
@ -65,7 +65,7 @@ $ docker-compose --profile all up -d
ZooKeeper 且不想启动新的服务,可以使用这个方式分别启动 DolphinScheduler 容器。
```shell
$ DOLPHINSCHEDULER_VERSION=3.1.0
$ DOLPHINSCHEDULER_VERSION=3.1.1
# 初始化数据库,其确保数据库 <DATABASE> 已经存在
$ docker run -d --name dolphinscheduler-tools \
-e DATABASE="postgresql" \
@ -126,4 +126,4 @@ $ docker run -d --name dolphinscheduler-alert-server \
## 环境变量
可以通过环境变量来修改 Docker 运行的配置,我们在沿用已有的 PostgreSQL 和 ZooKeeper 服务中就通过环境变量修改了 Docker 的数据库配置和
注册中心配置,关于全部的配置环境可以查看[全部的配置文件](https://github.com/apache/dolphinscheduler/blob/3.1.0/script/env/dolphinscheduler_env.sh) 了解 <!-- markdown-link-check-disable-line -->
注册中心配置,关于全部的配置环境可以查看[全部的配置文件](https://github.com/apache/dolphinscheduler/blob/3.1.1/script/env/dolphinscheduler_env.sh) 了解 <!-- markdown-link-check-disable-line -->

View File

@ -4,6 +4,10 @@
#### 以下是Apache DolphinScheduler每个稳定版本的设置说明。
### Versions: 3.1.1
#### Links [3.1.1 文档](../3.1.1/user_doc/about/introduction.md)
### Versions: 3.1.0
#### Links [3.1.0 文档](../3.1.0/user_doc/about/introduction.md)

View File

@ -989,7 +989,7 @@ CREATE TABLE t_ds_version
-- Records of t_ds_version
-- ----------------------------
INSERT INTO t_ds_version
VALUES ('1', '3.1.0');
VALUES ('1', '3.1.1');
-- ----------------------------

View File

@ -980,7 +980,7 @@ CREATE TABLE `t_ds_version` (
-- ----------------------------
-- Records of t_ds_version
-- ----------------------------
INSERT IGNORE INTO `t_ds_version` VALUES ('1', '3.1.0');
INSERT IGNORE INTO `t_ds_version` VALUES ('1', '3.1.1');
-- ----------------------------

View File

@ -971,7 +971,7 @@ INSERT INTO t_ds_queue(queue_name, queue, create_time, update_time)
VALUES ('default', 'default', '2018-11-29 10:22:33', '2018-11-29 10:22:33');
-- Records of t_ds_queue,default queue name : default
INSERT INTO t_ds_version(version) VALUES ('3.1.0');
INSERT INTO t_ds_version(version) VALUES ('3.1.1');
--
-- Table structure for table t_ds_plugin_define

View File

@ -1 +1 @@
3.1.0
3.1.1

View File

@ -32,7 +32,7 @@ if sys.version_info[0] < 3:
logger = logging.getLogger(__name__)
version = "3.1.0"
version = "3.1.1"
# Start package required
prod = [

View File

@ -18,7 +18,6 @@
"""Test Task class function."""
import logging
import re
from unittest.mock import patch
from typing import Set
from unittest.mock import patch