|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: 2017-12-14
Based on Jenkins
Rolling release Security release
Security advisory * Security Advisory 2017-12-14
+ Fixes the security issues described in the advisory.
CloudBees Internal Ticket: [TIGER-3987]
There may be incompatible JVM flags that are left over from a previous install of CJE.
If you have upgraded, and Operations Center fails to come up during the
upgrade process, manually remove the following flags from the files
You can use any editor to remove each of these items from anywhere within the file.
CloudBees Internal Ticket: [TIGER-4051]
We found a major compatibility issue with NFS v3.x. At this time, do not install or upgrade to CJE
1.11.1if you are using a NFS v3.x server.
CloudBees Internal Ticket: [TIGER-2355]
If you enter an invalid Managed Master image location under the Manage Jenkins page on Operations Center, when deploying the new instance, the log window will only show that it’s attempting to deploy and will not give any further feedback. Correct the image location to resolve this.
CloudBees Internal Ticket: [TIGER-2371]
CJE allows you to enable using one-shot executors. These provide slightly faster provisioning of the executors. However, the current implementation of one-shot executors doesn’t support pipeline resumption.
CloudBees Internal Ticket: [TIGER-2426]
CJE doesn’t support installing the Palace Cloud Plugin into masters that are not managed by CloudBees Jenkins Enterprise.
CloudBees Internal Ticket: [TIGER-2522]
Managed Masters may appear to be not accessible when Operations Center is being upgraded. This issue occurs when the internal application router is being updated and is a temporary condition.
CloudBees Internal Ticket: [TIGER-2724]
When deleting a Managed Master, the data associated with the master is retained in a backup snapshot used for recovery purposes. If you add a new master with the same name, it will recover the data from the snapshot and re-create it.
CloudBees Internal Ticket: [TIGER-2427]
[AWS] A CJE
cluster-recoverfails if its subnet is created in another availability zone. When using the operation
cluster-recover, it is simpler to keep the cluster in the same AWS availability zone (AZ).
CloudBees Internal Ticket: [TIGER-3414]
CJE can fail to upgrade when a worker was incompletely set up.
Under some circumstances, a
cje prepare worker-add operation can fail.
The typical case (on Amazon) is when the user’s MFA code is incorrectly
entered when prompted after the "apply" step. This results in a worker
that is incompletely set up and the instance isn’t started.
When this condition exists, an upgrade will fail.
To resolve this, use the
cje prepare worker-remove on the partially
created workers, and then restart the upgrade process.
CloudBees Internal Ticket: [TIGER-3539]
[AWS] Under some circumstances, an unexpected file prevents the operation
cluster-destroyfrom completing on AWS.
When destroying a cluster, CJE can also delete the S3 buckets, but a
docker.tar.gz may be present in the bucket which prevents CJE
from finishing. To work around this issue, manually delete the file
using the aws CLI and apply the cje operation again.
CloudBees Internal Ticket: [TIGER-3739]
If Operations Center is not running, you will be unable to use the cli to remove workers. If a worker configuration is damaged, Operations Center won’t start properly. In the event of this situation, please contact CloudBees customer support for assistance in resolving this.
CloudBees Internal Ticket: [TIGER-3957]
[anywhere] the cluster destroy operation does not remove /etc/.*_installed files in the target machine instances.
These files will interfere with a subsequent installation if you re-use the same machine instances.
To work around this delete the files, OR, re-install the OS for the machine instances.