Jenkins is widely recognized as the most feature-rich CI available with easy configuration, continuous delivery and continuous integration support, easily test, build and stage your app, and more. It supports multiple SCM tools including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based projects as well as arbitrary scripts.

https://jenkins.io

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-jenkins/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Jenkins Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 2-debian-10, 2.222.3-debian-10-r10, 2, 2.222.3, latest (2/debian-10/Dockerfile)

Subscribe to project updates by watching the bitnami/jenkins GitHub repo.

To run this application you need Docker Engine >= 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-jenkins/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

$ docker network create jenkins-network

$ docker volume create --name jenkins_data
$ docker run -d --name jenkins \
  -p 80:8080 -p 443:8443 \
  --network jenkins-network \
  --volume jenkins_data:/bitnami/jenkins \
  bitnami/jenkins:latest

Access your application at http://your-ip/

If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.

For persistence you should mount a volume at the /bitnami/jenkins path. The above examples define a docker volume namely jenkins_data. The Jenkins application state will persist as long as this volume is not removed.

To avoid inadvertent removal of this volume you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

This requires a minor change to the docker-compose.yml file present in this repository:

  ...
  services:
    jenkins:
    ...
    volumes:
-     - 'jenkins_data:/bitnami/jenkins    
+     - /path/to/jenkins-persistence:/bitnami/jenkins 
- volumes:
-   jenkins_data:
-     driver: local

$ docker network create jenkins-network

$ docker run -d --name jenkins \
  -p 80:8080 -p 443:8443 \
  --network jenkins-network \
  --volume /path/to/jenkins-persistence:/bitnami/jenkins \
  bitnami/jenkins:latest

For customizations, please note that this image is, by default, a non-root container using the user jenkins with uid=1001.

To pass and download a set of plugins and their dependencies, use the install-plugins.sh script. It will download them from update centers

NOTE: Default update centers must have Internet access

Use plugin artifact ID, without -plugin extension, and append the version if needed separated by :. Dependencies that are already included in the Jenkins war file will only be downloaded if their required version is newer than the one already included.

You can also use a custom version specifier:

• latest - download the latest version from the main update center. For Jenkins LTS images (example: git:latest)

You can run the script manually in the Dockerfile by adding the following after the COPY rootfs / command:

RUN /install-plugins.sh docker-slaves github-branch-source:1.8

Furthermore, it is possible to pass a file that contains this set of plugins (with or without line breaks), you should locate this file in the rootfs directory.

RUN /install-plugins.sh < /plugins.txt

You can include files to the image automatically. All files/directories located in /usr/share/jenkins/ref are copied to JENKINS_HOME.

We can create custom groovy scripts and make Jenkins run them at start up. We can also enforce them to run at a certain order by using a prefix in the names.

However, using this feature will disable the default configuration done by the Bitnami scripts. This is intended to customize the Jenkins configuration by code.

$ mkdir jenkins-init.groovy.d
$ echo "println '--> hello world!'" >jenkins-init.groovy.d/AA_hello.groovy
$ echo "println '--> bye world!'" >jenkins-init.groovy.d/BA_bye.groovy

$ docker run -d --name jenkins -e "DISABLE_JENKINS_INITIALIZATION=yes" -v "$(pwd)/jenkins-init.groovy.d:/usr/share/jenkins/ref/init.groovy.d" -p 80:8080 -p 443:8443 bitnami/jenkins:latest

$ docker exec jenkins ls /opt/bitnami/jenkins/jenkins_home/init.groovy.d
AA_hello.groovy
BA_bye.groovy

$ docker exec jenkins cat /opt/bitnami/jenkins/logs/jenkins.log | grep world
--> hello world!
--> bye world!

We can download plugins in a local folder and install them at run time.

$ docker run \
  --volume "$(pwd)/jenkins-plugins:/usr/share/jenkins/ref/plugins" \
  bitnami/jenkins:latest \
  install-plugins.sh \
    role-strategy:latest

$ docker run -d --name jenkins \
  -p 80:8080 -p 443:8443 \
  --volume "$(pwd)/jenkins-plugins:/usr/share/jenkins/ref/plugins" \
  bitnami/jenkins:latest

$ docker exec jenkins ls /opt/bitnami/jenkins/jenkins_home/plugins/

We can make Jenkins run our own config.xml file.

However, using this feature will disable the default configuration done by the Bitnami scripts. This is intended to customize the Jenkins configuration by code.

In the example below we are going to use a role-based authorization strategy by default.

$ docker run \
  --volume "$(pwd)/jenkins-plugins:/usr/share/jenkins/ref/plugins" \
  bitnami/jenkins:latest \
  install-plugins.sh \
    role-strategy:latest

$ cat >config.xml <<EOF
<?xml version='1.1' encoding='UTF-8'?>
<hudson>
  <disabledAdministrativeMonitors/>
  <version>2.138.1</version>
  <numExecutors>2</numExecutors>
  <mode>NORMAL</mode>
  <useSecurity>true</useSecurity>
  <authorizationStrategy class="com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy">
    <roleMap type="projectRoles"/>
    <roleMap type="globalRoles">
      <role name="admin" pattern=".*">
        <permissions>
          <permission>hudson.model.View.Delete</permission>
          <permission>hudson.model.Computer.Connect</permission>
          <permission>hudson.model.Run.Delete</permission>
          <permission>hudson.model.Computer.Create</permission>
          <permission>hudson.model.View.Configure</permission>
          <permission>hudson.model.Computer.Build</permission>
          <permission>hudson.model.Item.Configure</permission>
          <permission>hudson.model.Hudson.Administer</permission>
          <permission>hudson.model.Item.Cancel</permission>
          <permission>hudson.model.Item.Read</permission>
          <permission>hudson.model.Computer.Delete</permission>
          <permission>hudson.model.Item.Build</permission>
          <permission>hudson.scm.SCM.Tag</permission>
          <permission>hudson.model.Item.Move</permission>
          <permission>hudson.model.Item.Discover</permission>
          <permission>hudson.model.Hudson.Read</permission>
          <permission>hudson.model.Item.Create</permission>
          <permission>hudson.model.Item.Workspace</permission>
          <permission>hudson.model.Computer.Provision</permission>
          <permission>hudson.model.Run.Replay</permission>
          <permission>hudson.model.View.Read</permission>
          <permission>hudson.model.View.Create</permission>
          <permission>hudson.model.Item.Delete</permission>
          <permission>hudson.model.Computer.Configure</permission>
          <permission>hudson.model.Computer.Disconnect</permission>
          <permission>hudson.model.Run.Update</permission>
        </permissions>
        <assignedSIDs>
          <sid>admin</sid>
        </assignedSIDs>
      </role>
      <role name="viewer" pattern=".*">
        <permissions>
          <permission>hudson.model.Hudson.Read</permission>
          <permission>hudson.model.Item.Read</permission>
          <permission>hudson.model.Item.Discover</permission>
          <permission>hudson.model.View.Read</permission>
        </permissions>
        <assignedSIDs>
          <sid>authenticated</sid>
        </assignedSIDs>
      </role>
    </roleMap>
    <roleMap type="slaveRoles"/>
  </authorizationStrategy>
  <disableRememberMe>false</disableRememberMe>
  <projectNamingStrategy class="jenkins.model.ProjectNamingStrategy$DefaultProjectNamingStrategy"/>
  <workspaceDir>${JENKINS_HOME}/workspace/${ITEM_FULL_NAME}</workspaceDir>
  <buildsDir>${ITEM_ROOTDIR}/builds</buildsDir>
  <jdks/>
  <viewsTabBar class="hudson.views.DefaultViewsTabBar"/>
  <myViewsTabBar class="hudson.views.DefaultMyViewsTabBar"/>
  <clouds/>
  <scmCheckoutRetryCount>0</scmCheckoutRetryCount>
  <views>
    <hudson.model.AllView>
      <owner class="hudson" reference="../../.."/>
      <name>all</name>
      <filterExecutors>false</filterExecutors>
      <filterQueue>false</filterQueue>
      <properties class="hudson.model.View$PropertyList"/>
    </hudson.model.AllView>
  </views>
  <primaryView>all</primaryView>
  <slaveAgentPort>-1</slaveAgentPort>
  <label></label>
  <crumbIssuer class="hudson.security.csrf.DefaultCrumbIssuer">
    <excludeClientIPFromCrumb>false</excludeClientIPFromCrumb>
  </crumbIssuer>
  <nodeProperties/>
  <globalNodeProperties/>
</hudson>
EOF

$ docker run -d --name jenkins \
  -p 80:8080 -p 443:8443 \
  --env "DISABLE_JENKINS_INITIALIZATION=yes" \
  --volume "$(pwd)/jenkins-plugins:/usr/share/jenkins/ref/plugins" \
  --volume "$(pwd)/config.xml:/usr/share/jenkins/ref/config.xml" \
  bitnami/jenkins:latest

NOTE: We are using a config.xml created by Jenkins at first run. You can consider using groovy scripts to perform this kind of configuration too.

NOTE: We are not creating the admin user with this setup. It should be done separately.

You might need to customize the JVM running Jenkins, typically to pass system properties or to tweak heap memory settings. Use the JAVA_OPTS environment variable for this purpose:

$ docker run -d --name jenkins -p 80:8080 -p 443:8443 \
  --env JAVA_OPTS=-Dhudson.footerURL=http://mycompany.com \
  bitnami/jenkins:latest

By default, when running this image, Bitnami implement some logic in order to configure it for working out of the box. This initialization consists of creating the user and password, preparing data to persist, installing some plugins, configuring permissions, creating the JENKINS_HOME, etc. You can skip it in two ways:

• Setting the DISABLE_JENKINS_INITIALIZATION environment variable to yes.
• Attaching a volume with a custom JENKINS_HOME that contains a functional Jenkins installation.

Bitnami provides up-to-date versions of Jenkins, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the Jenkins container.

$ docker pull bitnami/jenkins:latest

• For docker-compose: $ docker-compose stop jenkins
• For manual execution: $ docker stop jenkins

$ rsync -a /path/to/jenkins-persistence /path/to/jenkins-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

You can use this snapshot to restore the application state should the upgrade fail.

• For docker-compose: $ docker-compose rm -v jenkins
• For manual execution: $ docker rm -v jenkins

• For docker-compose: $ docker-compose up jenkins
• For manual execution (mount the directories if needed): docker run --name jenkins bitnami/jenkins:latest

The Jenkins instance can be customized by specifying environment variables on the first run. The following environment values are provided to customize Jenkins:

• JENKINS_USERNAME: Jenkins admin username. Default: user
• JENKINS_PASSWORD: Jenkins admin password. Default: bitnami
• JENKINS_HOME: Jenkins home directory. Default: /opt/bitnami/jenkins/jenkins_home
• DISABLE_JENKINS_INITIALIZATION: Allows to disable the initial Bitnami configuration for Jenkins. Default: no
• JAVA_OPTS: Customize JVM parameters. No defaults.

Modify the docker-compose.yml file present in this repository:

jenkins:
  ...
  environment:
    - JENKINS_PASSWORD=my_password
  ...

$ docker run -d --name jenkins \
  -p 80:8080 -p 443:8443 \
  --network jenkins-network \
  --env JENKINS_PASSWORD=my_password \
  --volume jenkins_data:/bitnami/jenkins \
  bitnami/jenkins:latest

• Java distribution has been migrated from AdoptOpenJDK to OpenJDK Liberica. As part of VMware, we have an agreement with Bell Software to distribute the Liberica distribution of OpenJDK. That way, we can provide support & the latest versions and security releases for Java.

• The Jenkins container has been migrated to a "non-root" user approach. Previously the container ran as the root user and the Jenkins service was started as the jenkins user. From now on, both the container and the Jenkins service run as user jenkins (uid=1001). You can revert this behavior by changing USER 1001 to USER root in the Dockerfile.
• Consequences:
  • Backwards compatibility is not guaranteed when data is persisted using docker or docker-compose. We highly recommend migrating your Jenkins data ensuring the jenkins user has the appropiate permissions.
  • No "privileged" actions are allowed anymore.

• Use Jetty instead of Tomcat as web server.

• The Jenkins container has been migrated to the LTS version. From now on, this repository will only track long term support releases from Jenkins.

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version (docker version)
• Output of docker info
• Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright 2015-2020 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.