Jenkins : Liberty profile


Jenkins works on all released versions of the Liberty profile, however it works best with the latest version (at the time of writing that was the copy shipped as a part of WebSphere Application Server v8.5.5.) and these instructions are based on 8.5.5.


There are two ways to deploy Jenkins to the Liberty profile.


To install Jenkins on Liberty profile, simply copy jenkins.war to ${server.config.dir}/dropins, then access http://yourhost:9080/jenkins.


To install Jenkins on Liberty profile copy jenkins.war to ${server.config.dir}/apps. Edit the server.xml to add

<webApplication location="jenkins.war" />

then access http://youhost:9080/jenkins.


Simply overwrite your jenkins.war with the new version. Liberty profile should automatically redeploy the application.

Setting JVM options

Before starting Liberty profile create a ${server.config.dir}/jvm.options file and add the following line:


Additionally, add the following lines to ensure HTTP requests without Content-Type header are decoded correctly (JENKINS-62987):


This file can also be used to increase the heap size. On a new line add:


Securing Jenkins on Liberty profile

To configure the user/group to role mappings in Liberty profile you need to deploy it via the server.xml. Users and groups can be picked up from LDAP, or can be stored in the server.xml.

  1. Configure security by enabling the appSecurity-2.0 feature. This is done by editing the server.xml to add:

  2. Configure the role mapping for the Jenkins application:

    <webApplication location="jenkins.war">
        <security-role name="admin">
          <user name="jenkins-admin"/>
          <group name="jenkins-admins"/>
  3. Optional: Configure user in server.xml

    <basicRegistry realm="jenkins">
      <user name="jenkins-admin" password="secret"/>
      <group name="jenkins-admins">
        <member name="jenkins-admin">

    The securityUtility script in the bin folder can be used to generate a hashed password for this file. This can be done by running

    $ ${wlp.install.dir}/bin/securityUtility encode --encoding=hash secret

    Copy the printed hashed password into the password attribute in the server.xml. If secret is not passed in on the command line you will be prompted for it.

    Related reads

Relevant Issues