t4skforce/jenkins-ssl

By t4skforce

•Updated over 1 year ago

Fork of jenkins:latest, Jenkins HTTPS secured Web-UI, Oracle Java 8, Maven.

Image

10K+

Overview Tags

t4skforce/jenkins-ssl repository overview

⁠jenkins-ssl

Docker Container - Jenkins HTTPS secured Web-UI, Oracle Java 8, Maven. GitHub repo⁠

⁠About the Container

This build is based on jenkins/jenkins:latest⁠ with added features:

HTTPS Secured WEB-UI (4096bit - RSA)
OpenJDK 8u72

⁠How to use this image

docker run --name jenkins-master -p 443:8443 -p 50000:50000 t4skforce/jenkins-ssl:latest This will store the workspace in /var/jenkins_home. All Jenkins data lives in there - including plugins and configuration. You will probably want to make that a persistent volume (recommended):

docker run --name jenkins-master -p 443:8443 -p 50000:50000 -v /your/home:/var/jenkins_home t4skforce/jenkins-ssl:latest This will store the jenkins data in /your/home on the host. Ensure that /your/home is accessible by the jenkins user in container (jenkins user - uid 1000) or use -u some_other_user parameter with docker run.

You can also use a volume container:

docker run --name myjenkins -p 443:8443 -p 50000:50000 -v /var/jenkins_home t4skforce/jenkins-ssl:latest

Then jenkins-master container has the volume (please do read about docker volume handling to find out more).

⁠Opening Web-UI

https://yourservernameorip/⁠

⁠Upgrade

# download updates
docker pull t4skforce/jenkins-ssl:latest
# stop current running image
docker stop jenkins-master
# remove container
docker rm jenkins-master
# start with new base image
docker run --name jenkins-master -d -p 443:8443 -p 50000:50000 -v /your/home:/var/jenkins_home t4skforce/jenkins-ssl:latest

⁠Autostart

To enable Jankins to start at system-startup we need to create a systemd service file vim /lib/systemd/system/jenkins.service:

[Unit]
Description=Jenkins-Server
Requires=docker.service
After=docker.service

[Service]
Restart=always
ExecStart=/usr/bin/docker start -a jenkins-master
ExecStop=/usr/bin/docker stop -t 2 jenkins-master

[Install]
WantedBy=multi-user.target

To start the service manually call systemctl start jenkins. For retreaving the current service status call systemctl status jenkins

root@jenkins:~# systemctl status jenkins
● jenkins.service - Jenkins-Server
   Loaded: loaded (/lib/systemd/system/jenkins.service; enabled)
   Active: active (running) since Sun 2016-04-17 11:42:57 BST; 2s ago
 Main PID: 2642 (docker)
   CGroup: /system.slice/jenkins.service
           └─2642 /usr/bin/docker start -a jenkins-master

And last but not least we need to enable our newly created service via issuing systemctl enable jenkins:

root@jenkins:~# systemctl enable jenkins
Created symlink from /etc/systemd/system/multi-user.target.wants/jenkins.service to /lib/systemd/system/jenkins.service.

⁠Auto Upgrade

Combine all the above and autoupgrade the container at defined times. This requires you to at least setup Autostart⁠.

First we need to generate your upgrade shell script vim /root/jenkins_upgrade.sh:

#!/bin/bash

# Jenkins home directory on Server to save all the stuff
JENKINS_HOME="/your/home"

# download updates
docker pull t4skforce/jenkins-ssl:latest
# stop current running image
docker stop jenkins-master
# remove container
docker rm jenkins-master
# start with new base image
docker run --name jenkins-master -d -p 443:8443 -p 50000:50000 -v ${JENKINS_HOME}:/var/jenkins_home t4skforce/jenkins-ssl:latest t4skforce/jenkins-ssl:latest
# stop container
docker stop jenkins-master
# start via service
systemctl start jenkins

Next we need to make this file executable chmod +x /root/jenkins_upgrade.sh, and test if the upgrade script works by calling the shell-script and checking the service status afterwards:

root@jenkins:~# /root/jenkins_upgrade.sh
root@jenkins:~# systemctl status jenkins
● jenkins.service - Jenkins-Server
   Loaded: loaded (/lib/systemd/system/jenkins.service; enabled)
   Active: active (running) since Sun 2016-04-17 11:42:57 BST; 2s ago
 Main PID: 2642 (docker)
   CGroup: /system.slice/jenkins.service
           └─2642 /usr/bin/docker start -a jenkins-master

Now we need to set the trigger for the upgrade. In this example we just setup a weekly upgrade via crontab scheduled for Sunday at midnight. We add 0 0 * * 7 root /root/jenkins_upgrade.sh to /etc/crontab. The resulting file looks like:

# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
# Jenkins Docker Container Upgrade
0  0    * * 7   root    /root/jenkins_upgrade.sh
#

⁠Further Information

For further information on configuring the Image please refer to jenkins/jenkins:latest⁠

Tag summary

Recent tags

Content type

Image

Digest

sha256:f04d0eaf5…

Size

267.5 MB

Last updated

over 1 year ago

docker pull t4skforce/jenkins-ssl