文章目錄
- jenkins
- 1.先說說CI/CD
- 2.jenkins介紹
- 3.jenkins包下載
- 4.jenkins部署
- 5.jenkins手動部署java專案
- 6.jenkins自動部署java專案
- 7.jenkins腳本語法擴展
jenkins
1.先說說CI/CD

生產環境下,提前需要備份,再操作
集成:個人研發的部分與軟體整體部分交付的程序,代碼集成流程:編譯,測驗,打包
CI(continuous Integration):持續集成,在持續集成環境中,開發人員將會頻繁的提交代碼到主干,這些新提交在最終合并到主線之前,都需要通過編譯和自動化測驗流進行驗證,這樣做是基于之前持續集成程序中很重視自動化測驗驗證結果,以保障所有的提交在合并主線之后的質量問題,對可能出現的一些問題進行預警,一般用于測驗環境和開發環境,
CD:代碼持續互動,持續交付就是講我們的應用發布出去的程序,這個程序可以確保我們盡可能快的實作交付,這就意味著除了自動化測驗,我們還需要有自動化的發布流,以及通過一個按鍵就可以隨時隨地實作應用的部署上線,
持續部署的程序要手動部署
而jenkins中提供的插件可以實作CI/CD功能
幾種發布流程場景:



2.jenkins介紹
jenkins官網
jenkins是一個開源軟體專案,是基于java開發的一種持續集成工具,用于監控持續重復的作業,提供一個開放易用的軟體平臺,使軟體專案可以持續集成,
jenkins可以在每個人git代碼后,自動檢測到代碼的變動,自動的打包,測驗,提交,出現問題會以郵件的方式提醒,
3.jenkins包下載


4.jenkins部署
[root@jenkins ~]# systemctl disable --now firewalld
Removed /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
[root@jenkins ~]# setenforce 0
#下載jenkins.war包
[root@jenkins ~]# wget https://get.jenkins.io/war-stable/2.303.2/jenkins.war
#下載openJDK環境
[root@jenkins ~]# yum -y install java-17-openjdk*
#下載tomcat包
[root@jenkins ~]# wget https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.54/bin/apache-tomcat-9.0.54.tar.gz
#部署jenkins專案
[root@jenkins ~]# tar -xf apache-tomcat-9.0.54.tar.gz -C /usr/local/
[root@jenkins ~]# ln -s /usr/local/apache-tomcat-9.0.54/ /usr/local/jenkins
[root@jenkins ~]# mkdir /backup
[root@jenkins ~]# cp -r /usr/local/jenkins/webapps/* /backup/ #備份webapps下默認的目錄
[root@jenkins ~]# rm -rf /usr/local/jenkins/webapps/*
[root@jenkins ~]# cd /usr/local/jenkins/webapps/
[root@jenkins webapps]# cp /root/jenkins.war . #war包傳到webapps專案中
[root@jenkins webapps]# ls
jenkins.war
[root@jenkins webapps]# /usr/local/jenkins/bin/catalina.sh start #開啟tomcat也就是jenkins專案
Using CATALINA_BASE: /usr/local/jenkins
Using CATALINA_HOME: /usr/local/jenkins
Using CATALINA_TMPDIR: /usr/local/jenkins/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/local/jenkins/bin/bootstrap.jar:/usr/local/jenkins/bin/tomcat-juli.jar
Using CATALINA_OPTS:
Tomcat started.
[root@jenkins webapps]# ls
jenkins jenkins.war #會發現war包自動解壓了
進行jenkins訪問









#jenkins國內源
https://mirrors.tuna.tsinghua.edu.cn/jenkins/updates/update-center.json

全域工具內配置

maven中pom,jar,war
1.pom是maven依賴檔案
2.jar是java普通專案打包檔案
3.war是javaweb專案打包檔案
系統配置


5.jenkins手動部署java專案
| 版本 | 服務 | ip |
|---|---|---|
| centos8 | jenkins | 192.168.136.129 |
| centos8 | tomcat | 192.168.136.233 |
發布java專案的步驟
1.拉取代碼并且打包
git clone xx
mvn clean package
2.提前做好專案備份
3.war包傳到目標服務器上的webapps目錄中(做免密登錄)
4.重啟目標服務器的tomcat服務(會自動解壓包)
5.修改專案的配置
6.重啟tomcat服務
5.1jenkins服務開啟
#啟動jenkins
[root@jenkins ~]# /usr/local/jenkins/bin/catalina.sh start
Using CATALINA_BASE: /usr/local/jenkins
Using CATALINA_HOME: /usr/local/jenkins
Using CATALINA_TMPDIR: /usr/local/jenkins/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/local/jenkins/bin/bootstrap.jar:/usr/local/jenkins/bin/tomcat-juli.jar
Using CATALINA_OPTS:
Tomcat started.
[root@jenkins ~]# ss -antl
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 5 127.0.0.1:631 0.0.0.0:*
LISTEN 0 128 0.0.0.0:111 0.0.0.0:*
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 5 [::1]:631 [::]:*
LISTEN 0 1 [::ffff:127.0.0.1]:8005 *:*
LISTEN 0 128 [::]:111 [::]:*
LISTEN 0 100 *:8080 *:*
LISTEN 0 128 [::]:22 [::]:*
瀏覽器登錄到jenkins界面
先來模擬一個自帶的hello world小專案





5.2java開發人員已經把代碼放在了gitee倉庫,我們第一步應該開始拉代碼并且打包
#下載git(拉代碼用),maven(打包用)
[root@jenkins ~]# yum -y install git maven
#拉取代碼
[root@jenkins src]# git clone https://gitee.com/forgotten/tomcat-java-demo.git
正克隆到 'tomcat-java-demo'...
remote: Enumerating objects: 558, done.
remote: Counting objects: 100% (558/558), done.
remote: Compressing objects: 100% (316/316), done.
remote: Total 558 (delta 217), reused 558 (delta 217), pack-reused 0
接收物件中: 100% (558/558), 5.08 MiB | 771.00 KiB/s, 完成.
處理 delta 中: 100% (217/217), 完成.
#進行打包
[root@jenkins src]# cd tomcat-java-demo/
[root@jenkins tomcat-java-demo]# mvn clean package
[root@jenkins tomcat-java-demo]# ls
db deploy.yaml Dockerfile jenkinsfile LICENSE pom.xml README.md src target(包在此目錄下)
[root@jenkins tomcat-java-demo]# cd target/
[root@jenkins target]# ls
classes ly-simple-tomcat-0.0.1-SNAPSHOT maven-archiver
generated-sources ly-simple-tomcat-0.0.1-SNAPSHOT.war maven-status
#jenkins做免密登錄
[root@jenkins target]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:q0QOr+cNeRCkbnWDw8AuSG7txPMHh/SwQvgRqFOpz2M root@jenkins
The key's randomart image is:
+---[RSA 3072]----+
| o+o . |
| +oo.B . |
|++=.+ @ o |
|=o.O.= * . |
|.+o.B = S |
| Eo * + . |
| . . B o |
| o.= |
| .oo . |
+----[SHA256]-----+
[root@jenkins target]# ssh-copy-id root@192.168.136.233
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '192.168.136.233 (192.168.136.233)' can't be established.
ECDSA key fingerprint is SHA256:z1v69UX9NnT1/ikGZRDxB+Yeqgwi2YRfOMJ1t5ZTHtU.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@192.168.136.233's password:
Number of key(s) added: 1
Now try logging into the machine, with: "ssh 'root@192.168.136.233'"
and check to make sure that only the key(s) you wanted were added.
#jenkins服務器上將打包好的war包,傳到tomcat服務器上
[root@jenkins ~]# scp /usr/src/tomcat-java-demo/target/ly-simple-tomcat-0.0.1-SNAPSHOT.war 192.168.136.233:/usr/local/tomcat/webapps/
ly-simple-tomcat-0.0.1-SNAPSHOT.war 100% 17MB 217.8MB/s 00:00
#tomcat服務器上查看
[root@tomcat ~]# cd /usr/local/tomcat/webapps/
[root@tomcat webapps]# ls
docs examples host-manager ly-simple-tomcat-0.0.1-SNAPSHOT.war manager ROOT
#修改包的名字
[root@tomcat webapps]# mv ly-simple-tomcat-0.0.1-SNAPSHOT.war clq.war
#啟動tomcat服務
[root@tomcat webapps]# /usr/local/tomcat/bin/catalina.sh start
#再次查看,專案包會自動解壓
[root@tomcat webapps]# ls
clq clq.war docs examples host-manager manager ROOT

6.jenkins自動部署java專案
| 版本 | 服務 | ip |
|---|---|---|
| centos8 | jenkins | 192.168.136.129 |
| centos8 | tomcat | 192.168.136.233 |
配置jenkins中的tests專案

腳本修改為(公有倉庫拉取進行部署)
pipeline {
agent any
stages {
stage('Build') {
steps {
// Get some code from a GitHub repository
git 'https://gitee.com/forgotten/tomcat-java-demo.git'
// Run Maven on a Unix agent.
sh "mvn -Dmaven.test.failure.ignore=true clean package"
// To run Maven on a Windows agent, use
// bat "mvn -Dmaven.test.failure.ignore=true clean package"
}
}
}
}
如果報Could not initialize class sun.nio.fs.LinuxNativeDispatcher錯誤
解決方法:重啟jenkins服務,再次執行即可


最終腳本修改
pipeline {
agent any
stages {
stage('Build') {
steps {
// 此處git拉取的是不用輸入用戶和郵箱的java代碼塊
git 'https://gitee.com/forgotten/tomcat-java-demo.git'
// Run Maven on a Unix agent.
sh "mvn -Dmaven.test.failure.ignore=true clean package"
sh "mv target/ly-simple-tomcat-0.0.1-SNAPSHOT.war target/app.war"
// To run Maven on a Windows agent, use
// bat "mvn -Dmaven.test.failure.ignore=true clean package"
}
}
stage("publish"){
steps{
// 備份資料,第一次沒有資料的時候可以先注釋掉,之后打開就行
sh "ssh root@192.168.136.233 'tar -Jcf /opt/backup/app-\$(date +%Y%m%d).tar.xz /usr/local/tomcat/webapps/clq'"
//傳war包到目標服務器上
sh "scp target/app.war root@192.168.136.233:/usr/local/tomcat/webapps/"
//重啟 tomcat
sh "ssh root@192.168.136.233 '/usr/local/tomcat/bin/catalina.sh stop;sleep 3; /usr/local/tomcat/bin/catalina.sh start'"
}
}
}
}
構建運行


以上是拉取的公開的倉庫,如果是要拉取私有的倉庫呢



最后復制生成的連接粘貼到腳本中的git這一行命令就完工了
7.jenkins腳本語法擴展
流水線腳本擴展
簡單結構語法:
stages{
stage(''){
steps{
commands
}
}
}
#常規命令的寫法:
sh "mvn -Dmaven.test.failure.ignore=true clean package"
sh "mv target/ly-simple-tomcat-0.0.1-SNAPSHOT.war target/app.war"
#命令3點寫法:
sh '''
mvn -Dmaven.test.failure.ignore=true clean package
mv target/ly-simple-tomcat-0.0.1-SNAPSHOT.war target/app.war
'''
#環境變數的使用
environment{
DISABLE_AUTH = 'true'
DB_ENGINE = 'sqlite'
}
stages{
stage('hello'){
steps{
echo DISABLE_AUTH
echo DB_ENGINE
}
}
}
#清理和通知
#post部分會在pipeline結束的時候運行,所以可以添加通知去完成步驟清理
#deleteDir是固定寫法,可以清理workspace目錄下的檔案
post{
always{
deleteDir()
}
success{
echo '清理成功'
}
failure{
echo '清理失敗'
}
}
#電子郵箱
post{
failure{
mail to: '主題',
subject: "Failed Pipeline: ${currentBuild.fullDisplayName}",
body: "XXX ${env.BUILD_URL}"
}
}
#部署(重點)
#持續交付肯定會有3個階段,構建,測驗,部署,穩定的構建和測驗階段是任何部署的前提
pipeline{
agent any
stages{
stage('Build'){
steps{
echo '命令1'
}
}
stage('Test'){
steps{
echo '命令2'
}
}
stage('Deploy') {
steps{
echo '命令3'
}
}
}
}
#input命令會等待你的確認命令
轉載請註明出處,本文鏈接:https://www.uj5u.com/qita/335342.html
標籤:其他
上一篇:Python 計算機視覺(六)—— OpenCV 進行影像量化與采樣
下一篇:Linux三個小作業
