docker利用WebHook實現持續集成

2024-09-01 13:53:39

字體：大中小

來源：轉載

供稿：網友

研發小伙伴可能對下列操作步驟會深有體會

寫代碼--》提交代碼--》打包--》發布

在項目調試測試階段，可能經常需要重復上面的步驟，以便將最新代碼部署到特定環境供測試人員或其他人員使用

CI即持續集成的提出及各種解決方案，減輕了很多最初簡單但繁瑣的工作

本文將通過提交代碼到git，然后通過webHook觸發jenkins打包并發布到相應容器中，開發人員只需提交代碼，后續打包發布都自動實現

git　　：我使用的碼云我的主頁為： https://gitee.com/xiaochangwei

jenkins：Jenkins ver. 2.89.2

tomcat 8 jdk8 maven3.5

[root@iZnz7e74o4ag3oZ webapps]# java -versionjava version "1.8.0_121"Java(TM) SE Runtime Environment (build 1.8.0_121-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)[root@iZnz7e74o4ag3oZ webapps]# mvn -versionApache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T03:39:06+08:00)Maven home: /usr/local/src/mavenJava version: 1.8.0_121, vendor: Oracle CorporationJava home: /usr/local/src/jdk/jreDefault locale: en_US, platform encoding: UTF-8OS name: "linux", version: "3.10.0-693.2.2.el7.x86_64", arch: "amd64", family: "unix"[root@iZnz7e74o4ag3oZ webapps]#

配置好環境后，在tomcat中運行jenkins，并設置好用戶名密碼確保能正常登錄使用

docker,持續集成,webhook

操作步驟：

1.安裝插件 Generic Webhook Trigger Plugin、Deploy to container Plugin、Git plugin 由于這里暫時未發布到docker中，通過Deploy to container Plugin發布到tomcat中的

2.上傳maven項目到https://gitee.com

3.jenkins中新建項目ci

　　3.1 配置提交的代碼地址，Add有權限的用戶名和密碼（我的是私有項目），指定分支

docker,持續集成,webhook

　　3.2：配置maven命令以及發布到的tomcat

docker,持續集成,webhook

　　注意：發布項目的tomcat需要設置用戶信息，即修改conf下的user.xml 具體可以參考我很早之前寫的 http://www.cnblogs.com/xiaochangwei/p/4952644.html

這樣就可以手動構建項目了，請確保手動構建能成功后再進行下列操作

　　遇見的問題及解決方案：

　　　　如果構建時提示權限不對

　　　　生成公鑰： ssh-keygen -t rsa 一直回車直結束

　　　　cat ~/.ssh/id_rsa.pub 將內容增加到碼云上

docker,持續集成,webhook

　　　　如果還提示沒權限

　　　　手動先在jenkins運行的機器上clone一次代碼如 git clone git@gitee.com:xiaochangwei/ci-demo.git 注意輸入yes

docker,持續集成,webhook

　　　　然后再看.ssh目錄，多了一個known_hosts 里面有碼云了，然后再手動構建，應該就能成功了

docker,持續集成,webhook

　　至此，手動打包并部署就已經實現了

　　------------------------------自動部署 --------------------------------------------------

　　1. 安裝上述插件后勾選Generic Webhook Trigger 增加post參數 ref expression值為 $.ref 注意有個點

docker,持續集成,webhook

　　增加optional filter

docker,持續集成,webhook

　　其實上面這部分不用設置也行，尤其是只會在jenkins中部署一個項目的一個分支時，只需要勾選上Generic Webhook Trigger就可以的

　　2. 在碼云中增加hook：http://USER ID:API TOKEN@jenkins部署的地址:端口號/jenkins/generic-webhook-trigger/invoke （紅色這部分不要變）

　　　　(這里不用api token 直接用jenkins的登錄密碼也可以， api token查看地址為：jenkins-用戶-點擊用戶名-api token)

　　　　同時勾選push或者其他你認為需要觸發部署的事件

docker,持續集成,webhook

　　提交后點擊測試，如果返回ok，則表示成功，切換到jenkins，查看項目是否能夠自動部署

　　我自己寫了一個接口用來獲取點擊測試后，到底請求了些什么　　

docker,持續集成,webhook

　　　　格式化下內容如下：

{ "hook_name": "push_hooks", "total_commits_count": 1, "before": "0000000000000000000000000000000000000000", "user_name": "肖哥哥", "project": {  "path": "ci-demo",  "git_svn_url": "svn://gitee.com/xiaochangwei/ci-demo",  "path_with_namespace": "xiaochangwei/ci-demo",  "name": "ci-demo",  "namespace": "xiaochangwei",  "default_branch": "master",  "git_http_url": "https://gitee.com/xiaochangwei/ci-demo.git",  "name_with_namespace": "肖哥哥/ci-demo",  "url": "https://gitee.com/xiaochangwei/ci-demo",  "git_ssh_url": "git@gitee.com:xiaochangwei/ci-demo.git" }, "repository": {  "name": "ci-demo",  "description": "",  "url": "https://gitee.com/xiaochangwei/ci-demo.git",  "homepage": "https://gitee.com/xiaochangwei/ci-demo" }, "commits_more_than_ten": false, "ref": "refs/heads/master", "password": "", "commits": [{  "author": {   "name": "肖哥哥",   "time": "2015-11-06T13:21:07+08:00",   "email": "317409898@qq.com"  },  "id": "ec7159240a346fa5988913aa3057b902a4acb126",  "message": "A Test For WebHooks",  "url": "https://gitee.com/xiaochangwei/ci-demo/commit/ec7159240a346fa5988913aa3057b902a4acb126",  "timestamp": "2015-11-06T13:21:07+08:00" }], "after": "ec7159240a346fa5988913aa3057b902a4acb126", "user": {  "name": "肖哥哥",  "id": 372286,  "time": "2018-01-11T12:38:38+08:00",  "user": "xiaochangwei",  "email": "317409898@qq.com",  "url": "https://gitee.com/xiaochangwei" }}

　　其實多建立幾個項目然后獲取信息后會發現，不同項目間存在差異的就是project.git_ssh_url 和分支 ref

　　至此，單個項目的自動部署就完了

　　如果你在jenkins中有多個項目，你觸發其中的一個webHook你就會發現，所有的項目都在構建？

　　這就有點不科學了，本來只想構建A項目，結果Abc項目都構建了？要解決這個就需要用到上面提到的post param 和 filer 了

　　解析觸發自動構建的請求參數，ref和project.git_ssh_url是差異性的東西，那就根據兩個來區分項目

docker,持續集成,webhook

　　有這上面的兩個post參數還不行，因為只是獲取到了對應的參數值

　　其實要想區分不同的項目也簡單，只要獲取到的ref還有url 和需要構建的項目分支和 git地址相同就構建，否則就不構建

　　optional filter提供的方式就是最簡單的正則匹配

docker,持續集成,webhook

　　Expression設置為 ^(refs/heads/master)_(git@gitee.com:xiaochangwei/ci-demo.git)$ 注意修改為自己的項目地址

　　Text 設置為　　　$ref_$project.git_ssh_url

　　保存，再次構建，是不是只觸發了一個項目了，而不是所有項目了

　　測試：

　　　　1.提交代碼，提交代碼后看到jenkins就自動編譯打包了

　　　　　2.查看編譯日志：jenkins收到了webhook請求，并且拉取了代碼，提交信息和我們提交代碼時輸入信息一致　　　　　　

　　　　有同學質疑我這里為啥失敗了，是不是自動構建不可用，不是哈，我這里是用的阿里服務器，內存不夠導致了自動發布失敗

　　　　完整編譯并正確部署的日志如下：

Generic CauseBuilding in workspace /root/.jenkins/workspace/ciGenericWebhookEnvironmentContributor Received:{"before":"0000000000000000000000000000000000000000","after":"ec7159240a346fa5988913aa3057b902a4acb126","ref":"refs/heads/master","user_name":"/u8096/u54e5/u54e5","user":{"id":372286,"email":"317409898@qq.com","name":"/u8096/u54e5/u54e5","user":"xiaochangwei","url":"https://gitee.com/xiaochangwei","time":"2018-01-12T08:56:18+08:00"},"repository":{"name":"ci-demo","url":"https://gitee.com/xiaochangwei/ci-demo.git","description":"","homepage":"https://gitee.com/xiaochangwei/ci-demo"},"commits":[{"id":"ec7159240a346fa5988913aa3057b902a4acb126","message":"A Test For WebHooks","timestamp":"2015-11-06T13:21:07+08:00","url":"https://gitee.com/xiaochangwei/ci-demo/commit/ec7159240a346fa5988913aa3057b902a4acb126","author":{"name":"/u8096/u54e5/u54e5","email":"317409898@qq.com","time":"2015-11-06T13:21:07+08:00"}}],"project":{"name":"ci-demo","path":"ci-demo","url":"https://gitee.com/xiaochangwei/ci-demo","git_ssh_url":"git@gitee.com:xiaochangwei/ci-demo.git","git_http_url":"https://gitee.com/xiaochangwei/ci-demo.git","git_svn_url":"svn://gitee.com/xiaochangwei/ci-demo","namespace":"xiaochangwei","name_with_namespace":"/u8096/u54e5/u54e5/ci-demo","path_with_namespace":"xiaochangwei/ci-demo","default_branch":"master"},"total_commits_count":1,"commits_more_than_ten":false,"enterprise":null,"hook_name":"push_hooks","password":""}Contributing variables: ref = refs/heads/master project.git_ssh_url = git@gitee.com:xiaochangwei/ci-demo.git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url git@gitee.com:xiaochangwei/ci-demo.git # timeout=10Fetching upstream changes from git@gitee.com:xiaochangwei/ci-demo.git > git --version # timeout=10using GIT_ASKPASS to set credentials  > git fetch --tags --progress git@gitee.com:xiaochangwei/ci-demo.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 2eca30803759e021f658c92c136aa72dc026c3be (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2eca30803759e021f658c92c136aa72dc026c3beCommit message: "test auto package and deploy" > git rev-list --no-walk 2eca30803759e021f658c92c136aa72dc026c3be # timeout=10Parsing POMsEstablished TCP socket on 44276[ci] $ /usr/local/src/jdk/bin/java -cp /root/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven35-agent-1.12-alpha-1.jar:/usr/local/src/maven/boot/plexus-classworlds-2.5.2.jar:/usr/local/src/maven/conf/logging jenkins.maven3.agent.Maven35Main /usr/local/src/maven /usr/local/src/tomcat/webapps/jenkins/WEB-INF/lib/remoting-3.14.jar /root/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven35-interceptor-1.12-alpha-1.jar /root/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.12-alpha-1.jar 44276<===[JENKINS REMOTING CAPACITY]===>channel startedExecuting Maven: -B -f /root/.jenkins/workspace/ci/pom.xml clean package -Dmaven.test.skip=true[INFO] Scanning for projects...[INFO] [INFO] ------------------------------------------------------------------------[INFO] Building docker-demo 0.0.1-SNAPSHOT[INFO] ------------------------------------------------------------------------[INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ ci-demo ---[INFO] Deleting /root/.jenkins/workspace/ci/target[INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ci-demo ---[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 1 resource[INFO] Copying 0 resource[INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ci-demo ---[INFO] Changes detected - recompiling the module![INFO] Compiling 6 source files to /root/.jenkins/workspace/ci/target/classes[INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ ci-demo ---[INFO] Not copying test resources[INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ ci-demo ---[INFO] Not compiling test sources[INFO] [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ ci-demo ---[INFO] Tests are skipped.[INFO] [INFO] --- maven-war-plugin:2.6:war (default-war) @ ci-demo ---[INFO] Packaging webapp[INFO] Assembling webapp [ci-demo] in [/root/.jenkins/workspace/ci/target/ci-demo][INFO] Processing war project[INFO] Webapp assembled in [298 msecs][INFO] Building war: /root/.jenkins/workspace/ci/target/ci-demo.war[INFO] [INFO] --- spring-boot-maven-plugin:1.5.9.RELEASE:repackage (default) @ ci-demo ---[INFO] ------------------------------------------------------------------------[INFO] BUILD SUCCESS[INFO] ------------------------------------------------------------------------[INFO] Total time: 18.729 s[INFO] Finished at: 2018-01-12T08:56:46+08:00[INFO] Final Memory: 30M/72M[INFO] ------------------------------------------------------------------------Waiting for Jenkins to finish collecting data[JENKINS] Archiving /root/.jenkins/workspace/ci/pom.xml to com.xiao/ci-demo/0.0.1-SNAPSHOT/ci-demo-0.0.1-SNAPSHOT.pom[JENKINS] Archiving /root/.jenkins/workspace/ci/target/ci-demo.war to com.xiao/ci-demo/0.0.1-SNAPSHOT/ci-demo-0.0.1-SNAPSHOT.warchannel stoppedDeploying /root/.jenkins/workspace/ci/target/ci-demo.war to container Tomcat 8.x Remote with context /ci Redeploying [/root/.jenkins/workspace/ci/target/ci-demo.war] Undeploying [/root/.jenkins/workspace/ci/target/ci-demo.war] Deploying [/root/.jenkins/workspace/ci/target/ci-demo.war]Finished: SUCCESS

　　查看效果

docker,持續集成,webhook