To upgrade from one version of the Jenkins for DC/OS package to another, simply uninstall the current version, update your package repository cache, and install a new version.

  • Uninstall Jenkins as per the instructions in Uninstalling. Any builds that are currently in progress or queued will be lost.
  • Use the CLI to update your local cache of the package repository. dcos package update
  • Install Jenkins, again following the instructions on Customizing your install. Make sure you use the same configuration file as previously, specifically pointing Jenkins to the same host-volume.
  • Currently it is necessary to upgrade plugins by hand using the Jenkins UI at <dcos_url>/service/jenkins/pluginManager.

Upgrading to UCR Containerizer

This release supports the optional use of Universal Container Runtime (UCR) for the Jenkins Master which offers greater stability and emits metrics to the DC/OS Monitoring Service.

Customers can specify use of UCR via the following options:

    "advanced": {
        "containerizer": "MESOS"

Strict Mode Clusters with Volumes

Users with data on persistent volumes need to ensure the user running with the UCR containerizer must be able to read & write to the previously created persistent volumes.

It is strongly recommended that a backup of the persistent volume is performed before proceeding.

By default, the Docker containerizer uses the root user, and volumes may be populated by the root user. To upgrade to UCR in this scenario, the following steps need to be taken to allow UCR to read & write to volumes:

    "service": {
       "user": "root"