当前位置： 首页 > news >正文

网站建设公司前十名,周口市规划建设局网站,零食进货渠道网,网站建设优化排名文章目录 0、Jenkins卸载安装1、Jenkins配置2、后台启动脚本startup.sh3、后台关闭脚本stop.sh4、实时数据启动脚本startup.sh5、实时数据关闭脚本stop.sh6、jenkins制定完任务后#xff0c;点击立即构建#xff0c;控制台报错#xff08;…无法生成父级目录#xff09;7、… 文章目录 0、Jenkins卸载安装1、Jenkins配置2、后台启动脚本startup.sh3、后台关闭脚本stop.sh4、实时数据启动脚本startup.sh5、实时数据关闭脚本stop.sh6、jenkins制定完任务后点击立即构建控制台报错…无法生成父级目录7、Jenkins执行shell脚本权限不够8、构建好的jar包位置(可配置vim /etc/sysconfig/jenkins)9、target-display-front配置执行脚本10、maven项目Build - Goals and options11、target-display-server配置执行脚本12、send-socket配置执行脚本 0、Jenkins卸载安装 【Jenkins卸载】 # rpm卸载rpm -e jenkins

检查是否卸载成功rpm -ql jenkins

彻底删除残留文件find / -iname jenkins | xargs -n 1000 rm -rf【jenkins安装rpm先看7】 1、下载rpm地址https://mirrors.tuna.tsinghua.edu.cn/jenkins/redhat/?CMOAjenkins-2.401.3-1.1.noarch.rpm

2、cd /usr/local/jenkins 并输入rz命令上传rpm文件 3、安装rpm -ivh jenkins-……..noarch.rpm 【查看安装是否成功rpm -ql jenkins】 4、修改配置vim /etc/sysconfig/jenkinsJENKINS_PORT8777 5、配置jenkins的java路径whereis javavim /etc/init.d/jenkins下拉到candidates字段粘贴java的安装路径:wq保存退出刷新配置systemctl daemon-reload 6、启动systemctl start jenkins【报错了】systemctl status jenkins.service 查看错误解决不使用systemctl的方式操作Jenkins, 直接用Jenkins自带的服务启动 (使用 systemctl 最终也是执行的这个命令)切换到 Jenkins 脚本目录 cd /etc/init.d, 执行以下命令# 启动./jenkins start# 停止./jenkins stop# 状态./jenkins status【又报错了】-Jenkins版本过高了不支持java 8Starting Jenkins Running with Java 8 from /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.262.b10-1.el7.x86_64/jre, which is older than the minimum required version (Java 11).Supported Java versions are: [11, 17]See https://jenkins.io/redirect/java-support/ for more information.7、尝试下载老版本Jenkinshttps://jenkins.io/redirect/java-support/“从 6 月 28 日发布的 Jenkins 2.357 和即将发布的 9 月 LTS 版本开始Jenkins 最低需要 Java 11”下载2.357以下的Jenkins版本jenkins-2.346.3-1.1.noarch.rpm重复上面五个步骤8、无法启动jenkins通过systemctl start jenkins.service启动服务端口不是配置文件里自定义的端口vim /lib/systemd/system/jenkins.service# 修改端口号EnvironmentJENKINS_PORT8777 9、启动成功1、Jenkins配置 linux服务器需要配置maven环境、nodejs环境、npm环境下载对应的包并安装 Jenkins安装插件manage jenkins – plugins 搜索maven、nodejs 全局工具配置manage Jenkins – Global Tool Configuration 配置jdk/usr/local/jdk1.8.0_181 配置maven/usr/local/soft/apache-maven-3.5.4
2、后台启动脚本startup.sh #!/bin/bash #定义启动的jar包或者war包程序 application_nametargetdisplay-admin.jar #定义外部配置文件若不使用外部配置文件则将nohup开头的两行命令注释互换即打开下方被注释的nohup启动命令并注释当前nohup启动命令 #config_pathapplication.yml #定义日志文件 DIR/usr/local/soft/target_display_server application_port18080 log_namelog.txt echo Starting application \({application_name}... #nohup java -jar \){application_name} -Dspring.config.location\({config_path} \){log_name} 21 nohup java -jar \({DIR}/\){application_name} –server.port\({application_port} \){DIR}/\({log_name} 21 #nohup java -jar \){DIR}/\({application_name} --server.port\){application_port} /dev/null 21 #tail -f \({DIR}/\){log_name}

(hack) sleep 1 minute让项目跑起来

sleep 203、后台关闭脚本stop.sh

#!/bin/bash #定义关闭的jar包或者war包程序 application_nametargetdisplay-admin.jar PID\((ps -ef | grep /usr/local/soft/target_display_server/\){application_name} | grep -v grep | awk { print \(2 }) if [ -z \)PID ] thenecho \({application_name} is already stopped elseecho \){application_name} has killed,pid is \(PIDkill \)PID fi4、实时数据启动脚本startup.sh #!/bin/bash application_namesendSocket.jar DIR/usr/local/soft/sendsocket application_port18998 log_namelog.txt echo Starting application \({application_name}... #nohup java -jar \){application_name} -Dspring.config.location\({config_path} \){log_name} 21 nohup java -jar \({DIR}/\){application_name} –server.port\({application_port} \){DIR}/\({log_name} 21 #nohup java -jar \){DIR}/\({application_name} --server.port\){application_port} /dev/null 21 #tail -f \({DIR}/\){log_name}

(hack) sleep 1 minute让项目跑起来

sleep 205、实时数据关闭脚本stop.sh

#!/bin/bash application_namesendSocket.jar PID\((ps -ef | grep /usr/local/soft/sendsocket/\){application_name} | grep -v grep | awk { print \(2 }) if [ -z \)PID ] thenecho \({application_name} is already stopped elseecho \){application_name} has killed,pid is \(PIDkill \)PID fi6、jenkins制定完任务后点击立即构建控制台报错…无法生成父级目录 原因是 jenkins 使用的 jenkins 用户和组而 /data/maven/repository 的用户和组是 root。 解决方案改变repository的用户组为Jenkins即可 chown -R jenkins:jenkins /data/maven/repository7、Jenkins执行shell脚本权限不够 vim /usr/lib/systemd/system/jenkins.service 修改 Userroot Grouprootsystemctl daemon-reload systemctl restart jenkins8、构建好的jar包位置(可配置vim /etc/sysconfig/jenkins) /var/lib/jenkins/workspace/target-display-server/targetdisplay-admin/target/targetdisplay-admin.jar9、target-display-front配置执行脚本

remove dist

rm -rf /var/lib/jenkins/workspace/target-display-front/dist/* npm install npm run build cd /var/lib/jenkins/workspace/target-display-front/dist cp -rf ./index.html ./static /usr/local/soft/target_display_front10、maven项目Build - Goals and options clean package -Dmaven.test.skiptrue

maven 打包命令

mvn compile编译

mvn clean清除target

mvn package项目编译、单元测试、打包

mvn install项目编译、单元测试、打包、将打好的包部署到本地仓库在有多个项目互相依赖的情况下经常使用

mvn deploy项目编译、单元测试、打包、将打好的包部署到本地仓库、将打好的包部署到远程仓库

mvn [ package | install | deploy ] -DskipTests不执行测试用例但编译测试用例到对应的target下

mvn [ package | install | deploy ] -Dmaven.test.skip不执行测试用例也不编译测试用例11、target-display-server配置执行脚本

stop jar

sh /usr/local/soft/target_display_server/stop.sh

copy

cp -f /var/lib/jenkins/workspace/target-display-server/targetdisplay-admin/target/targetdisplay-admin.jar /usr/local/soft/target_display_server

Jenkins默认会在Build结束后Kill掉所有的衍生进程

BUILD_IDdontKillMe

start jar

sh /usr/local/soft/target_display_server/startup.sh12、send-socket配置执行脚本

stop jar

sh /usr/local/soft/sendsocket/stop.sh

copy

cp -f /var/lib/jenkins/workspace/send-socket/target/sendSocket.jar /usr/local/soft/sendsocket

Jenkins默认会在Build结束后Kill掉所有的衍生进程

BUILD_IDdontKillMe

start jar

sh /usr/local/soft/sendsocket/startup.sh