There are 3 files to place on your server – jenkins.war, pom.xml, and Procfile, each of them being on the same directory level on your server. The jenkins.war can be downloaded from the Jenkins site at https://jenkins-ci.org/. The pom.xml is very basic and has what the server needs to run the war. The Procfile contains the necessary commands to run the jenkins.war.
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.example</groupId> <version>1.0-SNAPSHOT</version> <artifactId>example-ci</artifactId> </project>
# Only listen on http; disable ajp and https web: java -jar jenkins.war --httpPort=$PORT --ajp13Port=-1 --httpsPort=-1
The files can be found at – https://github.com/melkybee/jenkins-ci.
Of course, this is just one way to install Jenkins on your server. Alternate ways to install it on your server (i.e., Ubuntu/Debian) can be found at the Jenkins website, https://jenkins-ci.org/.
At this point, Jenkins should be installed and running on your server. You’ll see the default Jenkins dashboard with the mustache guy at the top left. In part 2, we’ll set up all the basic configurations necessary in Jenkins and installing and integrating with GitHub.