DevOps Tools/CI/Jenkins - Revision history

R00t: /* Installation (CentOS 7 - using Repo) */

2020-08-18T17:58:36Z

‎Installation (CentOS 7 - using Repo)

2020-05-29T22:49:04Z

‎Installation using Apache/Tomcat (CentOS 7)

2019-10-25T18:00:52Z

2019-01-31T18:00:03Z

‎Backup Jenkins

2019-01-31T17:59:45Z

‎Backup Jenkins

2019-01-31T17:58:55Z

‎Backup Jenkins

2019-01-30T18:45:44Z

‎Backup Jenkins

2019-01-30T18:44:21Z

‎Backup Jenkins

2019-01-30T17:10:24Z

2019-01-04T19:36:02Z

@@ Line 84: / Line 84: @@
   <nowiki>~$ sudo yum install java-1.8.0-openjdk-devel -y
 ~$ curl --silent --location http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo | sudo tee /etc/yum.repos.d/jenkins.repo
-~$ sudo rpm --import https://jenkins-ci.org/redhat/jenkins-ci.org.key</nowiki>
+~$ sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key</nowiki>
 ===Install Jenkins===
   <nowiki>~$ sudo yum install jenkins</nowiki>

@@ Line 96: / Line 96: @@
 ==Installation using Apache/Tomcat (CentOS 7)==
 Download and install the latest version of CentOS 7.  I went with the Minimal install and below are the initial common packages.
-  <nowiki>~$ ~$ sudo yum install telnet net-tools vim tcpdump bind-utils redhat-lsb-core wget nfs-utils -y</nowiki>
+  <nowiki>~$ sudo yum install telnet net-tools vim tcpdump bind-utils redhat-lsb-core wget nfs-utils -y</nowiki>
 ===Download and Install===
 Install httpd, tomcat, and some of the dependencies

← Older revision		Revision as of 18:00, 25 October 2019
Line 352:		Line 352:
	# Except this file		# Except this file
	!.gitignore</nowiki>		!.gitignore</nowiki>
		+
		+	==Force kill job==
		+	Sometimes you need to force kill a job when the abort options do not work.<br>
		+	Using the Script Console you can execute arbitrary jenkins commands (Manage > Script Console)
		+	<nowiki>Jenkins.instance.getItemByFullName("JobName/FullProjectName")
		+	.getBuildByNumber(JobNumber)
		+	.finish(
		+	hudson.model.Result.ABORTED,
		+	new java.io.IOException("Aborting build")
		+	);
		+
		+	ie.
		+	Jenkins.instance.getItemByFullName("IE/TestProject")
		+	.getBuildByNumber(45)
		+	.finish(
		+	hudson.model.Result.ABORTED,
		+	new java.io.IOException("Aborting build")
		+	);
		+	</nowiki>

@@ Line 341: / Line 341: @@
 ==Backup Jenkins==
-'''NOTE:''' This does '''NOT''' retain file permissions or ownership.  Git only supports retention of the execution bit, nothing else. However, in a production environment, file permissions should not be handled by Git, they should be handled by something such as Puppet or Ansible.<br><br>
+'''NOTE:''' This does '''NOT''' retain file permissions or ownership.  Git only supports retention of the execution bit, nothing else. However, in a production environment, file permissions and ownership should not be handled by Git, they should be handled by something such as Puppet or Ansible.<br><br>
 The easiest way I've found to backup Jenkins is to copy the entire contents of '''<code>/var/lib/jenkins</code>''' to a SCM, such as GitLab.  This folder contains all the updates, plugins, users, and all other files.<br>
 However, this sounds easier than it is.  Jenkins has a handful of files and directories which only have root permissions, so if you need to rsync them to another host (which you may use Git from, like your laptop), you can do so with something like this.  Just make sure to do it from the Jenkins box as there are certain files that only root has permissions to.

@@ Line 341: / Line 341: @@
 ==Backup Jenkins==
-'''NOTE:''' This does '''NOT''' retain file permissions or ownership.  Git only supports retention of the execution bit, nothing else.<br><br>
+'''NOTE:''' This does '''NOT''' retain file permissions or ownership.  Git only supports retention of the execution bit, nothing else. However, in a production environment, file permissions should not be handled by Git, they should be handled by something such as Puppet or Ansible.<br><br>
 The easiest way I've found to backup Jenkins is to copy the entire contents of '''<code>/var/lib/jenkins</code>''' to a SCM, such as GitLab.  This folder contains all the updates, plugins, users, and all other files.<br>
 However, this sounds easier than it is.  Jenkins has a handful of files and directories which only have root permissions, so if you need to rsync them to another host (which you may use Git from, like your laptop), you can do so with something like this.  Just make sure to do it from the Jenkins box as there are certain files that only root has permissions to.

@@ Line 342: / Line 342: @@
 ==Backup Jenkins==
 The easiest way I've found to backup Jenkins is to copy the entire contents of '''<code>/var/lib/jenkins</code>''' to a SCM, such as GitLab.  This folder contains all the updates, plugins, users, and all other files.<br>
-However, this sounds easier than it is.  Jenkins has a handful of files and directories which only have root permissions, so if you need to SCP them to another host (which you may use Git from, like your laptop), you may need to rsync from the Jenkins host to the laptop with something like this:
+However, this sounds easier than it is.  Jenkins has a handful of files and directories which only have root permissions, so if you need to rsync them to another host (which you may use Git from, like your laptop), you can do so with something like this.  Just make sure to do it from the Jenkins box as there are certain files that only root has permissions to.
   <nowiki>~$ $ sudo rsync -r -a -vv -e ssh /var/lib/jenkins/ user@10.80.16.126:"/Users/user/Git/jenkins01/"</nowiki>
 From there, a normal <code>git add .</code> should add all the hidden files and folders to the git staging area.<br>

← Older revision		Revision as of 17:10, 30 January 2019
Line 338:		Line 338:
	icmp-blocks:		icmp-blocks:
	rich rules:</nowiki>		rich rules:</nowiki>
		+
		+
		+	==Backup Jenkins==
		+	The easiest way I've found to backup Jenkins is to copy the entire contents of '''<code>/var/lib/jenkins</code>''' to a SCM, such as GitLab. This folder contains all the updates, plugins, users, and all other files.<br>
		+	However, this sounds easier than it is. Jenkins has a handful of files and directories which only have root permissions, so if you need to SCP them to another host (which you may use Git from, like your laptop), you may need to SCP from the Jenkins host to the laptop with something like this:
		+	<nowiki>~$ $ sudo scp -r /var/lib/jenkins/. user@10.80.16.126:"/Users/user/Git/jenkins01/"</nowiki>
		+	From there, a normal <code>git add .</code> should add all the hidden files and folders to the git staging area.<br>
		+	'''NOTE:''' There may be some hidden folders that do not get added because they are empty. This is expected behavior with Git. You would need to add a file within the directory for it to be picked up, such as this:
		+	<nowiki>~$ sudo vim ./groovy/grapes/.gitignore
		+	# Ignore everything in this directory
		+	# *
		+	# Except this file
		+	!.gitignore</nowiki>

@@ 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/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/CI/Jenkins|Jenkins]]=
 ==Installation (Docker - OSX)==