CloudBees Jenkins Enterprise 1.11.9

2 minute read
CloudBees will no longer be supporting CloudBees Jenkins Enterprise 1.x after July 30, 2020. This end-of-life announcement allows CloudBees to focus on driving new technology and product innovation for CloudBees CI. For information on moving to CloudBees CI, please refer to CloudBees Jenkins Enterprise 1.x to CloudBees CI on modern cloud platforms migration guide which has been created to help you with the migration process. Existing customers can also contact their CSM to help ensure a smooth transition.

RELEASED: Public: 2018-08-15

Based on Jenkins LTS2.121.3-cb-1

Rolling release

New features

  • CloudBees Internal Ticket: [TIGER-4915]

    CJE 1 - Add Jenkins CLI commands to dump Mesos Build Agent Templates as JSON

  • CloudBees Internal Ticket: [TIGER-4984]

    Update embedded JVM in docker images to 1.8.0_171

Resolved issues

  • CloudBees Internal Ticket: [TIGER-5075]

    A user jenkins is always created on (build?) workers even if it is useless

  • CloudBees Internal Ticket: [TIGER-5058]

    Fix errors when retrieving support bundle

  • CloudBees Internal Ticket: [TIGER-4957]

    [CJE Anywhere] Support non "/etc/…​" ways to specify the proxy to install rpms on RHEL/Centos environments

  • CloudBees Internal Ticket: [TIGER-4924]

    Incorporate rebranded docker image names

  • CloudBees Internal Ticket: [TIGER-4880]

    Getting "operation not permitted" upon running 'cje run list-workers'

  • CloudBees Internal Ticket: [TIGER-4867]

    "Missing or invalid dna.env in .dna/servers/controller-1/dna.config" after cancelling support bundle creation

  • CloudBees Internal Ticket: [TIGER-4828]

    R3 instance type does not work any more

  • CloudBees Internal Ticket: [TIGER-4810]

    Allow to customise castle JVM options

  • CloudBees Internal Ticket: [TIGER-4400]

    A broken URL for the CJOC upgrade documentation replaced with a landing page for CJE 1 administration guide, CJE 1 upgrade documentation and CloudBees Core on Modern Platforms documentation.

  • CloudBees Internal Ticket: [TIGER-4970]

    [Anywhere] Support running ES as non-root

Elasticsearch runs as the user specified through storage.volume_user storage.volume_group and the corresponding nfs mount for backups is done as the same user.

The user can also be changed using the nfs-update operation if the cluster already exists.

Known issues

  • Release Notes

    Upgraded Palace Cloud Plugin from 2.0.8 to 2.0.9 in revision 2