CJE 1.11.2 has updated VM OS images (AMIs and OVAs) that integrate the security patches from OS vendors.
New installations of CJE that use these new images will get the patches automatically.
If you have an existing CJE deployment, you should update your CJE deployment to ensure that new machine instances get these patched OS images. After updating CJE, you should also follow these instructions to patch the existing images:
CJE Support Bundle now includes the output of the
cje status command
Simplify Managed Master/Operations Center containers' lifecycle management
[anywhere] / [nfs] NFS mount problems have been observed in some environments since the docker images for Managed Master and Operations Center is based on the Alpine Linux distribution.
For these cases, a new operation
nfs-update allows to modify NFS mount options, in particular to specify and explicit nfs version to use. NFS locking issue in
cloudbees/cje-oc:220.127.116.11 due Alpine version change. We suggest protocol version 3.
Prevent Castle from triggering a snapshot creation while another one is still pending
Remove JVM incompatible flags automatically when upgrading
Fixed issue where a
NullPointerException occur while editing the Managed Master configuration UI
Fixed issue where some installation files were not readable by a non-root user
Fix translation of
no_proxy parameter to the java system property
no_proxy, it results into
*.example.com being added to the
http.nonProxyHosts system property to have a matching behaviour.
If a docker image is not found during master provisioning, the user is not given any indication of the error
OneShot agents don't support pipeline resumption
Unable to execute jobs from Managed Master on CJE Worker
Masters go offline during Operations Center upgrade
Deleting a Managed Master from Operations Center does not actually delete it
cluster-recover fails if subnet is created on another availability zone
[aws] In some cases, destroying a cluster will hang on the S3 bucket deletion. A workaround is to manually delete the S3 bucket, then apply the operation again
It is not possible to remove workers when Operations Center is down
[anywhere] Cluster destroy does not remove