docker：（4）利用WebHook實現持續集成

時間  2019-11-08
標籤 docker 利用 webhook 實現 持續 集成 欄目 Docker 简体版
原文   原文鏈接

研發小夥伴可能對下列操做步驟會深有體會html

寫代碼--》提交代碼--》打包--》發佈java

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

CI即持續集成的提出及各類解決方案，減輕了不少最初簡單但繁瑣的工做git

本文將經過提交代碼到git，而後經過webHook觸發jenkins打包併發布到相應容器中，開發人員只需提交代碼，後續打包發佈都自動實現web

git　　：我使用的碼雲   個人主頁爲： https://gitee.com/xiaochangweispring

jenkins：Jenkins ver. 2.89.2docker

tomcat 8 jdk8 maven3.5express

[root@iZnz7e74o4ag3oZ webapps]# java -version
java 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 -version
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T03:39:06+08:00)
Maven home: /usr/local/src/maven
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/local/src/jdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.2.2.el7.x86_64", arch: "amd64", family: "unix"
[root@iZnz7e74o4ag3oZ webapps]#

配置好環境後，在tomcat中運行jenkins，並設置好用戶名密碼確保能正常登陸使用api

操做步驟：tomcat

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有權限的用戶名和密碼（個人是私有項目），指定分支

　　

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

　　

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

       這樣就能夠手動構建項目了，請確保手動構建能成功後再進行下列操做

　　碰見的問題及解決方案：

　　　　若是構建時提示權限不對

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

　　　　cat ~/.ssh/id_rsa.pub   將內容增長到碼雲上

　　　　

　　　　若是還提示沒權限

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

　　　　

　　　　而後再看.ssh目錄，多了一個known_hosts 裏面有碼雲了，而後再手動構建，應該就能成功了

　　　　

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

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

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

　　

　　增長optional filter

　　

　　其實上面這部分不用設置也行，尤爲是隻會在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或者其餘你認爲須要觸發部署的事件

　　

　　提交後點擊測試，若是返回ok，則表示成功，切換到jenkins，查看項目是否可以自動部署

　　我本身寫了一個接口用來獲取點擊測試後，到底請求了些什麼　　

　　格式化下內容以下：

{
    "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是差別性的東西，那就根據兩個來區分項目

　　

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

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

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

　　

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

　　Text 設置爲　　　$ref_$project.git_ssh_url

　　保存，再次構建，是否是隻觸發了一個項目了，而不是全部項目了

　　

　　測試：

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

　　　　　

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

　　　　有同窗質疑我這裏爲啥失敗了，是否是自動構建不可用，不是哈， 我這裏是用的阿里服務器，內存不夠致使了自動發佈失敗

　　　　完整編譯並正確部署的日誌以下：

　　　　

Generic Cause
Building in workspace /root/.jenkins/workspace/ci
GenericWebhookEnvironmentContributor 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=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git@gitee.com:xiaochangwei/ci-demo.git # timeout=10
Fetching upstream changes from git@gitee.com:xiaochangwei/ci-demo.git
 > git --version # timeout=10
using 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=10
Checking out Revision 2eca30803759e021f658c92c136aa72dc026c3be (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 2eca30803759e021f658c92c136aa72dc026c3be
Commit message: "test auto package and deploy"
 > git rev-list --no-walk 2eca30803759e021f658c92c136aa72dc026c3be # timeout=10
Parsing POMs
Established 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 started
Executing 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.war
channel stopped
Deploying /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

　　查看效果

　　

相關文章
相關標籤/搜索
每日一句
    每一个你不满意的现在，都有一个你没有努力的曾经。
本站公眾號
   歡迎關注本站公眾號,獲取更多信息
聯繫我們 最近搜索 最新文章 沪ICP备13005482号-10 MyBatis教程 SQL 教程 MySQL教程 Java 教程 Thymeleaf 教程 Hibernate教程 Spring教程 Redis教程