DevOps Tools/Integration/Jenkins Gitlab - Revision history

R00t: /* Jenkins with Gitlab */

2019-01-10T14:24:03Z

‎Jenkins with Gitlab

R00t: /* GitLab */

2019-01-09T23:01:29Z

‎GitLab

R00t: /* Webhook */

2019-01-09T22:50:55Z

‎Webhook

R00t: /* GitLab */

2019-01-09T22:45:25Z

‎GitLab

R00t: /* SELinux Policy */

2019-01-09T22:33:04Z

‎SELinux Policy

R00t at 22:31, 9 January 2019

2019-01-09T22:31:56Z

R00t: /* Jenkins Job */

2019-01-09T21:59:08Z

‎Jenkins Job

R00t at 21:55, 9 January 2019

2019-01-09T21:55:22Z

R00t at 21:23, 9 January 2019

2019-01-09T21:23:35Z

R00t: /* Jenkins with Gitlab */

2019-01-04T21:32:27Z

‎Jenkins with Gitlab

@@ Line 1: / Line 1: @@
 [[DevOps_Tools/Overview|Overview]] | [[DevOps_Tools/CI|Continuous Integration (CI)]] | [[DevOps_Tools/SCM|Source Control Management (SCM)]] | [[DevOps_Tools/Containerization|Containerization]] | [[DevOps_Tools/Configuration|Configuration]] | [[DevOps_Tools/Integration|Integration]]
 =[[DevOps_Tools/Integration/Jenkins_Gitlab|Jenkins with Gitlab]]=
-[https://medium.com/@teeks99/continuous-integration-with-jenkins-and-gitlab-fa770c62e88a reference]<br>
+[https://medium.com/@teeks99/continuous-integration-with-jenkins-and-gitlab-fa770c62e88a reference][https://github.com/jenkinsci/gitlab-plugin/wiki/Setup-Example reference#2]<br>
 Make sure that you have [[DevOps_Tools/CI/Jenkins#Jenkins|Jenkins]] and [[DevOps_Tools/SCM/GitLab#Git_Lab|Gitlab]] installed.

← Older revision		Revision as of 23:01, 9 January 2019
Line 156:		Line 156:
	*SSL verification		*SSL verification
	: [select] check box ('''Enable SSL verification''') if Jenkins is not using SSL.		: [select] check box ('''Enable SSL verification''') if Jenkins is not using SSL.
		+	====Troubleshooting====
		+	I encountered an error where GitLab could not connect to Jenkins because it was within the local network. In Gitlab, you have to specifically allow requests to the local network from hooks and services.
		+	*GitLab > [click] More > [click] Admin Area > [select] Settings > [click] Network > [select] Expand next to '''Outbound requests''' > [select] check box for ''Allow requests to the local network from hooks and services''

@@ Line 85: / Line 85: @@
 :: [select] check box
 :*; (Advanced) Secret Token
-:: [click] Generate and copy token somewhere you can use it later.
+:: [click] Generate and copy '''Jenkins Secret Token''' somewhere you can use it later.
 '''Post-Build Actions'''<br>
 *;[click] Add post-build-action > [select] Publish build status to Gitlab
@@ Line 144: / Line 144: @@
 ===GitLab===
 Now we need to add a webhook to gitlab so that gitlab can trigger the Jenkins Job.<br>
-'''Gitlab''' > [select] the Project > [select] Integrations > [Insert] Jenkins URL.
+'''Gitlab''' > [select] the Project > [select] Integrations

← Older revision		Revision as of 22:45, 9 January 2019
Line 143:		Line 143:

	===GitLab===		===GitLab===
		+	Now we need to add a webhook to gitlab so that gitlab can trigger the Jenkins Job.<br>
		+	'''Gitlab''' > [select] the Project > [select] Integrations > [Insert] Jenkins URL.

@@ Line 108: / Line 108: @@
       #Install the new policy file.
 </nowiki></pre>
 =====SELinux Boolean=====

@@ Line 90: / Line 90: @@
 ====Troubleshooting====
 While I was specifying the Git Repo URL in the '''Source Code Management''' section, I kept getting errors citing access failures to local resources on the Jenkins server.   Checking SELinux, I found it was blocking git and tomcat from accessing resources, so I made the following changes:
 ===GitLab===

@@ Line 51: / Line 51: @@
 '''NOTE:''' I was having problems getting Jenkins to connect to Gitlab and it turned out to be because I set the hostnames and URLs for both Jenkins and Gitlab to '''localhost''' (both were running as vms within virtualbox with port forwards).  After rebuilding both from scratch and defining FQDNs with host file entries for DNS, the gitlab connection was successful.
-==Jenkins Job==
+==Webhook==
 Now we want to setup a really basic webhook that will mark commits in gitlab as successful.  This is just an example, its not a very useful webhook.<br>
 Jenkins > [click] New Item > Specify item name > [click] Freestyle project
 '''General'''<br>
@@ Line 87: / Line 88: @@
 '''Post-Build Actions'''<br>
 *;[click] Add post-build-action > [select] Publish build status to Gitlab

← Older revision		Revision as of 21:55, 9 January 2019
Line 54:		Line 54:
	Now we want to setup a really basic webhook that will mark commits in gitlab as successful. This is just an example, its not a very useful webhook.<br>		Now we want to setup a really basic webhook that will mark commits in gitlab as successful. This is just an example, its not a very useful webhook.<br>
	Jenkins > [click] New Item > Specify item name > [click] Freestyle project		Jenkins > [click] New Item > Specify item name > [click] Freestyle project
		+	'''General'''<br>
		+	*;GitLab Connection
		+	:[select] Gitlab from the drop down
		+	*;GitLab Repository Name
		+	:enter in your repository name. Mine was ''project01''
		+	'''Source Code Management'''<br>
		+	*;Git
		+	:[select]
		+	:*;Repository URL
		+	::the URL of the remote repo. Same syntax as used with ''<code>git clone</code>''. Mine was ''git@gitlab01.r00tedvw.com:user/project01.git''
		+	:*;Credentials
		+	::the credentials of the Jenkins user that you added earlier.
		+	:*; (Advanced) Name
		+	::the ID of your repo. same name as you would use in ''<code>git remote</code>''. Mine was ''origin''
		+	:*; (Advanced) Refspec
		+	:: I have no idea what this stuff does yet. Mine was ''+refs/heads/:refs/remotes/origin/ +refs/merge-requests//head:refs/remotes/origin/merge-requests/''
		+	:*; Branches to build
		+	:: specify the branch you'd like to track. In my instance, I let Gitlab pass the branch name to jenkins as a variable, so I specified that instead. Mine was ''origin/${gitlabSourceBranch}''
		+	'''Build Triggers'''<br>
		+	* [select] Build when a change is pused to GitLab. GitLab webhook URL:
		+	:Make sure to copy the '''GitLab webhook URL''', you'll need it later.
		+	:*; Push Events
		+	:: [select] check box
		+	:*; Opened Merge Request Events
		+	:: [select] check box
		+	:*; Approved Merge Requests (EE-only)
		+	:: [select] check box
		+	:*; Comments
		+	:: [select] check box
		+	:*; (Advanced) Secret Token
		+	:: [click] Generate and copy token somewhere you can use it later.
		+	'''Post-Build Actions'''<br>
		+	*;[click] Add post-build-action > [select] Publish build status to Gitlab

← Older revision		Revision as of 21:23, 9 January 2019
Line 52:		Line 52:

	==Jenkins Job==		==Jenkins Job==
		+	Now we want to setup a really basic webhook that will mark commits in gitlab as successful. This is just an example, its not a very useful webhook.<br>
		+	Jenkins > [click] New Item > Specify item name > [click] Freestyle project