June 2023 – 一江春水向东流

SECURITY

koolshare梅林路由器提示含非法关键词，无法安装插件

错误提示：检测到离线安装包：含非法关键词！！！根据法律规定，koolshare软件中心将不会安装此插件！！！解决方案： 1. 在「系统管理」- 「系统设置」里面打开「Allow SSH password login」。 2. 在 a free SSH and telnet client for Windows 下载 Putty 并安装 3. 在 Putty 中使用路由器的 IP 地址来连接 4. 输入登录路由器的账号、密码 5. 输入

sed -i 's/\tdetect_package/\t# detect_package/g' /koolshare/scripts/ks_tar_install.sh

1	sed -i 's/\tdetect_package/\t# detect_package/g' /koolshare/scripts/ks_tar_install.sh

6. 重新离线安装违禁软件

By sean, 2 years06/19/2023 ago

HANDBOOK

10分钟搞定让你困惑的 Jenkins 环境变量

前言 Jenkins， DevOps 技术栈的核心之一，CI/CD 离不开编写 Pipeline 脚本，上手 Jenkins ，简单查一下文档，你就应该不会被 agent，stages，step 这类关键词弄懵，也能很快构建出 pipeline 的骨架但是当向骨架中填充内容的时候，尤其如何利用环境变量（系统内置｜自定义），多数人都会变得比较混乱，浪费很多时间，本文就帮助大家快速通关环境变量准备如果你想一边阅读本文，一边实践，但是没有 Jenkins 服务可用，又想快速尝试，可以应用 Docker 一个命令快速搭建 Jenkins 服务

docker container run --rm -p 8080:8080 -p 50000:50000 --name=jenkins -v $(pwd):/var/jenkins_home jenkins/jenkins

1	docker container run --rm -p 8080:8080 -p 50000:50000 --name=jenkins -v $(pwd):/var/jenkins_home jenkins/jenkins

2023年了，本地没有 Docker 说不过去了，过来瞧瞧 Docker 系列是否入得了你的法眼？打开浏览器输入：localhost:8080 找到终端的临时密码登陆安装推荐的依赖创建新的 Pipeline 类型的 Item 点击左侧 Config，然后在页面底部 Pipeline 部分输入我们接下来写的脚本进行测试就好了就是这么简单….. 认识 Jenkins 环境变量 Jenkins 环境变量就是通过 env 关键字暴露出来的全局变量，可以在 Jenkins 文件的任何位置使用其实和你使用的编程语言中的全局变量没有实质差别查看 Read more…

By sean, 2 years06/14/2023 ago

KUBERNETES

构建多种系统架构支持的 Docker 镜像

最新在信创项目中，经常需要构建支持amd64和arm64架构的镜像，而有的场景在同一个 Kubernetes 集群中的节点是混合架构的，也就是说，其中某些节点的 CPU 架构是 x86 的，而另一些节点是 ARM 的。为了让我们的镜像在这样的环境下运行，一种最简单的做法是根据节点类型为其打上相应的标签，然后针对不同的架构构建不同的镜像，比如 demo:v1-amd64 和 demo:v1-arm64，然后还需要写两套 YAML：一套使用 demo:v1-amd64 镜像，并通过 nodeSelector 选择 x86 的节点，另一套使用 demo:v1-arm64 镜像，并通过 nodeSelector 选择 ARM 的节点。很显然，这种做法不仅非常繁琐，而且管理起来也相当麻烦，如果集群中还有其他架构的节点，那么维护成本将成倍增加。你可能知道，每个 Docker 镜像都是通过一个 manifest 来描述的，manifest 中包含了这个镜像的基本信息，包括它的 mediaType、大小、摘要以及每一层的分层信息等。可以使用 docker manifest inspect 查看某个镜像的 manifest 信息：

$ docker manifest inspect aneasystone/hello-actuator:v1
{
        "schemaVersion": 2,
        "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
        "config": {
                "mediaType": "application/vnd.docker.container.image.v1+json",
                "size": 3061,
                "digest": "sha256:d6d5f18d524ce43346098c5d5775de4572773146ce9c0c65485d60b8755c0014"
        },
        "layers": [
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 2811478,
                        "digest": "sha256:5843afab387455b37944e709ee8c78d7520df80f8d01cf7f861aae63beeddb6b"
                },
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 928436,
                        "digest": "sha256:53c9466125e464fed5626bde7b7a0f91aab09905f0a07e9ad4e930ae72e0fc63"
                },
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 186798299,
                        "digest": "sha256:d8d715783b80cab158f5bf9726bcada5265c1624b64ca2bb46f42f94998d4662"
                },
                {
                        "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
                        "size": 19609795,
                        "digest": "sha256:112ce4ba7a4e8c2b5bcf3f898ae40a61b416101eba468397bb426186ee435281"
                }
        ]
}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

$ docker manifest inspect aneasystone/hello-actuator:v1

{

"schemaVersion": 2,

"mediaType": "application/vnd.docker.distribution.manifest.v2+json",

"config": {

"mediaType": "application/vnd.docker.container.image.v1+json",

"size": 3061,

"digest": "sha256:d6d5f18d524ce43346098c5d5775de4572773146ce9c0c65485d60b8755c0014"

},

"layers": [

{

"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",

"size": 2811478,

"digest": "sha256:5843afab387455b37944e709ee8c78d7520df80f8d01cf7f861aae63beeddb6b"

},

{

"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",

"size": 928436,

"digest": "sha256:53c9466125e464fed5626bde7b7a0f91aab09905f0a07e9ad4e930ae72e0fc63"

},

{

"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",

"size": 186798299,

"digest": "sha256:d8d715783b80cab158f5bf9726bcada5265c1624b64ca2bb46f42f94998d4662"

},

{

"mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",

"size": 19609795,

"digest": "sha256:112ce4ba7a4e8c2b5bcf3f898ae40a61b416101eba468397bb426186ee435281"

}

]

}

可以加上 –verbose 查看更详细的信息，包括该 manifest 引用的镜像标签和架构信息：

$ docker manifest inspect --verbose aneasystone/hello-actuator:v1
{
        "Ref": "docker.io/aneasystone/hello-actuator:v1",
        "Descriptor": {
                "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
                "digest": "sha256:f16a1fcd331a6d196574a0c0721688360bf53906ce0569bda529ba09335316a2",
                "size": 1163,
                "platform": {
                        "architecture": "amd64",
                        "os": "linux"
                }
        },
        "SchemaV2Manifest": {
                ...
        }
}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

$ docker manifest inspect --verbose aneasystone/hello-actuator:v1

{

"Ref": "docker.io/aneasystone/hello-actuator:v1",

"Descriptor": {

"mediaType": "application/vnd.docker.distribution.manifest.v2+json",

"digest": "sha256:f16a1fcd331a6d196574a0c0721688360bf53906ce0569bda529ba09335316a2",

"size": 1163,

"platform": {

"architecture": "amd64",

"os": "linux"

}

},

"SchemaV2Manifest": {

...

}

我们一般不会直接使用 manifest，而是通过标签来关联它，方便人们使用。从上面的输出结果可以看出，该 manifest 通过 docker.io/aneasystone/hello-actuator:v1 这个镜像标签来关联，支持的平台是 linux/amd64，该镜像有四个分层，另外注意这里的 mediaType 字段，它的值是 application/vnd.docker.distribution.manifest.v2+json，表示这是 Docker 镜像格式（如果是 application/vnd.oci.image.manifest.v1+json 表示 OCI 镜像）。可以看出这个镜像标签只关联了一个 manifest ，而一个 manifest 只对应一种架构；如果同一个镜像标签能关联多个 manifest ，不同的 manifest 对应不同的架构，那么当我们通过这个镜像标签启动容器时，容器引擎就可以自动根据当前系统的架构找到对应的 manifest 并下载对应的镜像。实际上这就是多架构镜像（ multi-arch Read more…

By sean, 2 years06/09/2023 ago

MIDDLEWARE

nginx反向代理Harbor/配置https

使用docker-compose安装harbor，配置ssl证书后使用nginx反向代理到harbor.配置后安装docker可以直接用域名登录harbor，无需配置私有仓库 nginx配置 1.修改harbor配置文件

hostname: ycr.yyiuap.com
http:
  port: 81
external_url: https://ycr.yyiuap.com

1

2

3

4

hostname: ycr.yyiuap.com

http:

port: 81

external_url: https://ycr.yyiuap.com

2.nginx配置

upstream harbor {
    server x.x.x.246:81;
}

server {
    listen 81;
    server_name ycr.yyiuap.com;
    location / {
        proxy_pass http://harbor;
        client_max_body_size 0;
        proxy_connect_timeout 90;
        proxy_read_timeout 90;
        proxy_buffer_size 4k;
        proxy_buffers 6 32k;
        proxy_busy_buffers_size 64k;
        proxy_temp_file_write_size 64k;
    }
}


server {
    listen       443 ssl;
    listen       [::]:443;
    server_name  ycr.yyiuap.com;

    ssl_certificate /usr/local/nginx/conf/certs/ycr.yyiuap.com/ycr.yyiuap.com.cert;
    ssl_certificate_key /usr/local/nginx/conf/certs/ycr.yyiuap.com/ycr.yyiuap.com.key;

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
    ssl_prefer_server_ciphers on;
    ssl_session_cache shared:SSL:10m;

    client_max_body_size 0;

    chunked_transfer_encoding on;

    location /v2/ {
      proxy_pass http://harbor/v2/;
      proxy_set_header Host $host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_buffering off;
      proxy_request_buffering off;
    }

    location / {
        proxy_pass http://harbor;
        client_max_body_size 0;
        proxy_connect_timeout 90;
        proxy_read_timeout 90;
        proxy_buffer_size 4k;
        proxy_buffers 6 32k;
        proxy_busy_buffers_size 64k;
        proxy_temp_file_write_size 64k;
        proxy_set_header Host $host:$server_port;
        proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_redirect http:// $scheme://;
    }
}

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

upstream harbor {

server x.x.x.246:81;

}

server {

listen 81;

server_name ycr.yyiuap.com;

location / {

proxy_pass http://harbor;

client_max_body_size 0;

proxy_connect_timeout 90;

proxy_read_timeout 90;

proxy_buffer_size 4k;

proxy_buffers 6 32k;

proxy_busy_buffers_size 64k;

proxy_temp_file_write_size 64k;

}

server {

listen 443 ssl;

listen [::]:443;

server_name ycr.yyiuap.com;

ssl_certificate /usr/local/nginx/conf/certs/ycr.yyiuap.com/ycr.yyiuap.com.cert;

ssl_certificate_key /usr/local/nginx/conf/certs/ycr.yyiuap.com/ycr.yyiuap.com.key;

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

ssl_prefer_server_ciphers on;

ssl_session_cache shared:SSL:10m;

client_max_body_size 0;

chunked_transfer_encoding on;

location /v2/ {

proxy_pass http://harbor/v2/;

proxy_set_header Host $host;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

proxy_set_header X-Forwarded-Proto $scheme;

proxy_buffering off;

proxy_request_buffering off;

}

location / {

proxy_pass http://harbor;

client_max_body_size 0;

proxy_connect_timeout 90;

proxy_read_timeout 90;

proxy_buffer_size 4k;

proxy_buffers 6 32k;

proxy_busy_buffers_size 64k;

proxy_temp_file_write_size 64k;

proxy_set_header Host $host:$server_port;

proxy_set_header X-Forwarded-For $remote_addr;

proxy_set_header X-Real-IP $remote_addr;

proxy_set_header X-Forwarded-Proto $scheme;

proxy_redirect http:// $scheme://;

}

另：创建证书脚本：

#!/bin/bash

registry_url="ycr.yyiuap.com"


# 生成使用的相关证书
openssl genrsa -out ca.key 4096

openssl req -x509 -new -nodes -sha512 -days 3650 \
    -subj "/C=CN/ST=Beijing/L=Beijing/O=example/OU=Personal/CN=$registry_url" \
    -key ca.key \
    -out ca.crt

openssl genrsa -out $registry_url.key 4096

openssl req -sha512 -new \
    -subj "/C=CN/ST=Beijing/L=Beijing/O=example/OU=Personal/CN=$registry_url" \
    -key $registry_url.key \
    -out $registry_url.csr

cat > v3.ext <<-EOF
authorityKeyIdentifier=keyid,issuer
basicConstraints=CA:FALSE
keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth
subjectAltName = @alt_names

[alt_names]
DNS.1=$registry_url
DNS.2=reg.yyuap
DNS.3=`hostname`
EOF

openssl x509 -req -sha512 -days 3650 \
    -extfile v3.ext \
    -CA ca.crt -CAkey ca.key -CAcreateserial \
    -in $registry_url.csr \
    -out $registry_url.crt

openssl x509 -inform PEM -in $registry_url.crt -out $registry_url.cert

mkdir -p /etc/docker/certs.d/$registry_url/

cp $registry_url.cert /etc/docker/certs.d/$registry_url/
cp $registry_url.key /etc/docker/certs.d/$registry_url/
cp ca.crt /etc/docker/certs.d/$registry_url/

#将证书加入系统级别信任
cp /etc/docker/certs.d/ca.crt /etc/pki/ca-trust/source/anchors/
update-ca-trust extract
systemctl daemon-reload && systemctl restart docker

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

#!/bin/bash

registry_url="ycr.yyiuap.com"

# 生成使用的相关证书

openssl genrsa -out ca.key 4096

openssl req -x509 -new -nodes -sha512 -days 3650 \

-subj "/C=CN/ST=Beijing/L=Beijing/O=example/OU=Personal/CN=$registry_url" \

-key ca.key \

-out ca.crt

openssl genrsa -out $registry_url.key 4096

openssl req -sha512 -new \

-subj "/C=CN/ST=Beijing/L=Beijing/O=example/OU=Personal/CN=$registry_url" \

-key $registry_url.key \

-out $registry_url.csr

cat > v3.ext <<-EOF

authorityKeyIdentifier=keyid,issuer

basicConstraints=CA:FALSE

keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment

extendedKeyUsage = serverAuth

subjectAltName = @alt_names

[alt_names]

DNS.1=$registry_url

DNS.2=reg.yyuap

DNS.3=`hostname`

EOF

openssl x509 -req -sha512 -days 3650 \

-extfile v3.ext \

-CA ca.crt -CAkey ca.key -CAcreateserial \

-in $registry_url.csr \

-out $registry_url.crt

openssl x509 -inform PEM -in $registry_url.crt -out $registry_url.cert

mkdir -p /etc/docker/certs.d/$registry_url/

cp $registry_url.cert /etc/docker/certs.d/$registry_url/

cp $registry_url.key /etc/docker/certs.d/$registry_url/

cp ca.crt /etc/docker/certs.d/$registry_url/

#将证书加入系统级别信任

cp /etc/docker/certs.d/ca.crt /etc/pki/ca-trust/source/anchors/

update-ca-trust extract

systemctl daemon-reload && systemctl restart docker

问题： docker pull ycr.yyiuap.com/base/golang:alphine-node-3 Error response from daemon: received unexpected HTTP status: 503 Service Unavailable 解决：去掉 http_proxy代理即可参考：https://blog.csdn.net/oscarun/article/details/121395218 1、request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)错误： [root@iZrj9j76z8dlull9vqa4tqZ ~]# docker pull harbor.xxx.cn:443/1-1/mytomcat:8.5.52 Error response from Read more…

By sean, 2 years06/09/2023 ago

KUBERNETES

docker下载镜像报错unknown method AddResource for service containerd.services.leases.v1.Leases: not implemented

导语：下载镜像到最后会提示unknown method AddResource: not implemented

<span class="pipeline-node-17">+ docker buildx build --output=type=local,name=openeuler,dest=./resources --platform=linux/amd64,linux/arm64 -f build/Dockerfile.os.openeuler .
#1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1
#1 pulling image moby/buildkit:buildx-stable-1 11.0s done
#1 creating container buildx_buildkit_multi-platform0 0.0s done
#1 ERROR: Error response from daemon: No such image: moby/buildkit:buildx-stable-1</span>

1

2

3

4

5

6

<span class="pipeline-node-17">+ docker buildx build --output=type=local,name=openeuler,dest=./resources --platform=linux/amd64,linux/arm64 -f build/Dockerfile.os.openeuler .

#1 [internal] booting buildkit

#1 pulling image moby/buildkit:buildx-stable-1

#1 pulling image moby/buildkit:buildx-stable-1 11.0s done

#1 creating container buildx_buildkit_multi-platform0 0.0s done

#1 ERROR: Error response from daemon: No such image: moby/buildkit:buildx-stable-1</span>

原因，安装完docker启动后，还需要重启一下containerd服务 sudo systemctl restart containerd.service sudo systemctl restart docker 参考https://blog.csdn.net/sinat_14840559/article/details/114399166

By sean, 2 years06/07/2023 ago

MIDDLEWARE

Jenkins迁移

以前的Jenkins是通过docker容器跑的：

/usr/bin/docker run \
  --network host \
  --restart=on-failure:5 \
  --name=jenkins \
  -u=root \
  -v /ali-nas/data/jenkins:/var/jenkins_home \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /usr/bin/docker:/usr/bin/docker \
  -v /usr/libexec/docker/cli-plugins:/usr/libexec/docker/cli-plugins \
  -v /root/.docker/buildx:/root/.docker/buildx \
  -v /usr/local/maven:/usr/local/maven \
  -v /lib64/:/lib64/ \
  -e PATH=/usr/local/maven/bin:/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$PATH \
  jenkins/jenkins:alpine

1

2

3

4

5

6

7

8

9

10

11

12

13

14

/usr/bin/docker run \

--network host \

--restart=on-failure:5 \

--name=jenkins \

-u=root \

-v /ali-nas/data/jenkins:/var/jenkins_home \

-v /var/run/docker.sock:/var/run/docker.sock \

-v /usr/bin/docker:/usr/bin/docker \

-v /usr/libexec/docker/cli-plugins:/usr/libexec/docker/cli-plugins \

-v /root/.docker/buildx:/root/.docker/buildx \

-v /usr/local/maven:/usr/local/maven \

-v /lib64/:/lib64/ \

-e PATH=/usr/local/maven/bin:/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$PATH \

jenkins/jenkins:alpine

此方法有一些不便，想迁移到tomcat原生方式运行首先下载安装包：

wget https://dlcdn.apache.org/tomcat/tomcat-9/v9.0.75/bin/apache-tomcat-9.0.75.tar.gz
wget https://get.jenkins.io/war-stable/2.401.1/jenkins.war

1 2	wget https://dlcdn.apache.org/tomcat/tomcat-9/v9.0.75/bin/apache-tomcat-9.0.75.tar.gz wget https://get.jenkins.io/war-stable/2.401.1/jenkins.war

将tomcat解压后，将jenkins.war放到webapps目录启动tomcat，打开页面报错404，查看localhost.log日志： java.lang.UnsupportedClassVersionError 原因是2.361.1以上版本的jenkins要求java11或java17，而本机为java8，而jenkins的2.401要求java11以后下载JDK:

wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz

1	wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz

创建启动文件：

cat /usr/lib/systemd/system/jenkins.service
[Unit]
Discription=tomcat server
After=network.target

[Service]
#User=tomcat
#Group=tomcat
WorkingDirectory=/data/jenkins/tomcat9
Environment="JAVA_HOME=/data/jenkins/jdk-11.0.2"
Environment="JENKINS_HOME=/data/jenkins/tomcat9/webapps"
Environment="JAVA_OPTS=-Djava.security.egd=file:///dev/urandom"
Environment="CATALINA_BASE=/data/jenkins/tomcat9"
Environment="CATALINA_HOME=/data/jenkins/tomcat9"
Environment="CATALINA_OPTS=-Xms1024M -Xmx10240M -server -XX:+UseParallelGC"
Type=forking
ExecStart=/data/jenkins/tomcat9/bin/startup.sh
ExecStop=/data/jenkins/tomcat9/bin/shutdown.sh
Restart=always

[Install]
WantedBy=multi-user.target

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

cat /usr/lib/systemd/system/jenkins.service

[Unit]

Discription=tomcat server

After=network.target

[Service]

#User=tomcat

#Group=tomcat

WorkingDirectory=/data/jenkins/tomcat9

Environment="JAVA_HOME=/data/jenkins/jdk-11.0.2"

Environment="JENKINS_HOME=/data/jenkins/tomcat9/webapps"

Environment="JAVA_OPTS=-Djava.security.egd=file:///dev/urandom"

Environment="CATALINA_BASE=/data/jenkins/tomcat9"

Environment="CATALINA_HOME=/data/jenkins/tomcat9"

Environment="CATALINA_OPTS=-Xms1024M -Xmx10240M -server -XX:+UseParallelGC"

Type=forking

ExecStart=/data/jenkins/tomcat9/bin/startup.sh

ExecStop=/data/jenkins/tomcat9/bin/shutdown.sh

Restart=always

[Install]

WantedBy=multi-user.target

在准备好必要的环境后，jenkins的迁移需要将jenkins主目录原有数据拷贝到新的机器或者新目录下，主要包含config.xml文件以及jobs、users、workspace、plugins四个目录，然后重启jenkins即可

cd /data/jenkins/tomcat9/webapps
\cp -r /ali-nas/data/jenkins/jobs/* .
\cp -r /ali-nas/data/jenkins/config.xml .
\cp -r /ali-nas/data/jenkins/users/* users/
\cp -r /ali-nas/data/jenkins/workspace .
\cp -r /ali-nas/data/jenkins/plugins/* plugins/

1

2

3

4

5

6

cd /data/jenkins/tomcat9/webapps

\cp -r /ali-nas/data/jenkins/jobs/* .

\cp -r /ali-nas/data/jenkins/config.xml .

\cp -r /ali-nas/data/jenkins/users/* users/

\cp -r /ali-nas/data/jenkins/workspace .

\cp -r /ali-nas/data/jenkins/plugins/* plugins/

By sean, 2 years06/06/2023 ago