作為持續整合的利器Jenkins已經得到了廣泛地應用，僅僅作為一個工具，Jenkins已然有了自己的生態圈，支援其的plugin更是超過1300+。在實際中如何使用以及如何更好地使用jenkins，一直是大家在實踐並討論的。本系列文章將會從如何使用jenkins方面對一些細節進行總結和整理，這篇文章將會介紹如何在Jenkins中實現與gitlab的整合

事前準備

只要有jenkins即可，沒有的可以使用Jenkins官方的映象或者安裝包，或者使用Easypack中封裝的基本一致的Jenkins。

docker pull映象

[[email protected] ~]# docker pull liumiaocn/jenkins
 

Using default tag: latest
latest: Pulling from liumiaocn/jenkins
Digest: sha256:87c954f71bc3ce1ba5d001bfbae501f9965368c16f0111ef951350376c2f6832
Status: Image is up to date for liumiaocn/jenkins:latest
[[email protected] ~]#

啟動Jenkins映象
docker run -d -p 8090:8080 -p 50000:50000 –name jenkins liumiaocn/jenkins

[root@liumiaocn ~]# docker run -d -p 8090:8080 -p 50000:50000 --name jenkins liumiaocn/jenkins
63dc2d52de03074858a6b61db4955345a66cfd436c5a47384924e9e3f8177778
[root@liumiaocn ~]#

plugin

與gitlab的整合也是通過外掛來做的,需要安裝GitLab Plugin外掛,目前版本是1.4.6，通過使用這個外掛進行整合能夠使得gitlab在push之後能夠呼叫jenkins進行構建。詳細說明如下圖所示

安裝

可以使用jenkins的外掛管理頁面進行安裝，也可以使用其id(gitlab-plugin)在映象中進行安裝並重啟映象即可。在mailer中我們也使用了jenkins官方所提供的install-plugins.sh，連同依賴關係一起安裝給自定義jenkins會帶來極大的方便。

[[email protected] ~]# docker exec -it jenkins sh
/ $ install-plugins.sh gitlab-plugin
Creating initial locks...
Analyzing war...
Downloading plugins...
Downloading plugin: gitlab-plugin from https://updates.jenkins.io/download/plugins/gitlab-plugin/latest/gitlab-plugin.hpi
 > gitlab-plugin depends on workflow-step-api:1.15,credentials:2.1.0,git:2.4.1,git-client:1.19.0,matrix-project:1.10,plain-credentials:1.1;resolution:=optional
Downloading plugin: workflow-step-api from https://updates.jenkins.io/download/plugins/workflow-step-api/latest/workflow-step-api.hpi
Downloading plugin: credentials from https://updates.jenkins.io/download/plugins/credentials/latest/credentials.hpi
Downloading plugin: git from https://updates.jenkins.io/download/plugins/git/latest/git.hpi
Downloading plugin: git-client from https://updates.jenkins.io/download/plugins/git-client/latest/git-client.hpi
Skipping optional dependency plain-credentials
Downloading plugin: matrix-project from https://updates.jenkins.io/download/plugins/matrix-project/latest/matrix-project.hpi
 > workflow-step-api depends on structs:1.5
Downloading plugin: structs from https://updates.jenkins.io/download/plugins/structs/latest/structs.hpi
 > matrix-project depends on junit:1.20,script-security:1.13
Downloading plugin: junit from https://updates.jenkins.io/download/plugins/junit/latest/junit.hpi
Downloading plugin: script-security from https://updates.jenkins.io/download/plugins/script-security/latest/script-security.hpi
 > credentials depends on structs:1.7
 > git depends on workflow-scm-step:1.14.2,credentials:2.1.13,git-client:2.4.0,mailer:1.18,matrix-project:1.7.1,parameterized-trigger:2.33;resolution:=optional,promoted-builds:2.27;resolution:=optional,scm-api:2.1.0,ssh-credentials:1.13,token-macro:1.12.1;resolution:=optional
Downloading plugin: workflow-scm-step from https://updates.jenkins.io/download/plugins/workflow-scm-step/latest/workflow-scm-step.hpi
Downloading plugin: mailer from https://updates.jenkins.io/download/plugins/mailer/latest/mailer.hpi
Skipping optional dependency parameterized-trigger
Skipping optional dependency promoted-builds
Downloading plugin: scm-api from https://updates.jenkins.io/download/plugins/scm-api/latest/scm-api.hpi
Skipping optional dependency token-macro
Downloading plugin: ssh-credentials from https://updates.jenkins.io/download/plugins/ssh-credentials/latest/ssh-credentials.hpi
 > junit depends on structs:1.2
 > git-client depends on credentials:2.1.13,ssh-credentials:1.13,structs:1.6
 > workflow-scm-step depends on workflow-step-api:2.9
 > ssh-credentials depends on credentials:2.1.0
 > mailer depends on display-url-api:1.0
Downloading plugin: display-url-api from https://updates.jenkins.io/download/plugins/display-url-api/latest/display-url-api.hpi

WAR bundled plugins:


Installed plugins:
credentials:2.1.14
display-url-api:2.0
git-client:2.4.6
git:3.3.1
gitlab-plugin:1.4.6
junit:1.20
mailer:1.20
matrix-project:1.11
scm-api:2.1.1
script-security:1.29
ssh-credentials:1.13
structs:1.9
workflow-scm-step:2.6
workflow-step-api:2.12
Cleaning up locks
/ $ exit
[[email protected] ~]# docker restart jenkins
jenkins
[[email protected] ~]#

外掛安裝確認

重新啟動後確認此外掛已經安裝完畢

設定內容

系統管理 -> 系統設定處的Gitlab相關內容則為所需設定的內容

認證資訊使用Gitlab的API Token的方式進行建立，首先確認一下Gitlab 的ApiToken的相關資訊。

gitlab API相關的資訊，可以參看：

使用確認到的API Token建立一個Gitlab API Token型別的Crendentials，詳細資訊如下：

在設定頁面選中剛剛建立的Gitlab API Token

驗證

設定完畢之後，點選Test Connection便可以確認jenkins和gitlab之間是否通過此外掛進行了整合。頁面顯示Success說明已經OK。

總結

Jenkins與gitlab設定需要下載並安裝gitlab-plugin外掛，通過建立gitlab api token並使用，便可以通過gitlab-plugin外掛提供的測試功能進行整合連線確認。