Running Jenkins in IBM LinuxONE Community Cloud OpenShift environment with WebSphere Application Server Liberty Profile

The IBM LinuxONE Community Cloud is a no-charge, 24 x 7, enterprise-grade, open access, shared public cloud environment on IBM's LinuxONE III platform (s390x)

You can request free trial for OpenShift Container Platform or provision a Virtual Machine on IBM LinuxONE Community Cloud here

---

This repository contains 2 docker files to use within Openshift environment to create a Jenkins instance.

Dockerfile-full

Uses a full (pre-packaged with features) image of WebSphere Application Server Liberty Profile (usually called wlp or liberty) for s390x. Jenkins 2.235.4 war file downloaded from official location and placed into dropins folder that is monitored for applications by default. jvm.options file copied from this repo with settings to:

• bypass initial Unlock Jenkins screen (which forces users to get temp password from container runtime)
• set default JENKINS_HOME location
• set maximum memory allocation pool (optional)
• avoid non-UTF text related errors (optional)

Recommended: If you want to have a persistent Jenkins configuration, mount a persistent storage to JENKINS_HOME location as a mount point. In jvm.options it is set to /opt/jenkins

Dockerfile-kernel

Uses a kernel (base) image of WebSphere Application Server Liberty Profile (usually called wlp or liberty) for s390x and requires configuration based on provided server.xml. Jenkins 2.235.4 war file downloaded from official location and placed into apps folder that is monitored for applications by default. jvm.options file copied from this repo with settings to:

• bypass initial Unlock Jenkins screen (which forces users to get temp password from container runtime)
• set default JENKINS_HOME location
• set maximum memory allocation pool (optional)
• avoid non-UTF text related errors (optional)

server.xml file copied from this repo with settings to:

• initialize jenkins.war from apps folder
• provide features list
• configure default server endpoint

configure.sh script launched at the end to install features listed in server.xml

Argument OPENJ9_SCC=false is set to ignore creation of SCC layer which takes a lot of resources and performs server stop && server start procedures twice.

Recommended: If you want to have a persistent Jenkins configuration, mount a persistent storage to JENKINS_HOME location as a mount point. In jvm.options it is set to /opt/jenkins

Dockerfile-kernel-addons

Same as Dockerfile-kernel-addons + additionally installing:

• NodeJS + NPM
• Git