|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-10-10
Based on Jenkins
CloudBees Internal Ticket: [TIGER-4118]
[Castle] Lazy umount has been replaced with a procedure killing remaining processes holding locks.
CloudBees Internal Ticket: [TIGER-5266]
[ubuntu] Fix a case where apt-cache content was stale, causing installation errors
CloudBees Internal Ticket: [TIGER-5189]
Fixed a proxy compatibility issue
CloudBees Internal Ticket: [TIGER-5142]
Fixed a case where adding a worker was failing after disabling ElasticSearch.
CloudBees Internal Ticket: [TIGER-5048]
Docker prune/clean up frequency is now customizable through
CloudBees Internal Ticket: [TIGER-5043]
Implemented a watchdog to enable/disable topbeat and logstash based on Elasticsearch availability.
CloudBees Internal Ticket: [TIGER-4044]
certificates-updateoperation now cleans up old custom certificates.
In versions 1.11.11 and 1.11.12, it is not possible to restart existing workers due to an issue when reconfiguring Docker. It is fixed in the 1.11.13 version.
[worker-1] Initializing Docker cleanup job [worker-1] "-":1: bad minute [worker-1] errors in crontab file, can't install.
Add the attribute
docker_image_clean_frequency = 60in
[worker]section as well as under any
[worker] docker_image_clean_frequency = 60
cje upgrade --config-only --forcecommand.