CJE was updated to use OpenJDK 8u131. It now uses the CloudBees's recommended Java parameters by default for its internal components, including the G1 garbage collector.
Existing installations should apply the new options to existing masters on an as needed basis.
This change makes CJE more secure, in that it further tightens the access controls provided to the docker containers running on the CJE cluster.
On AWS, CJE now supports Elastic Network Adapter (ENA) instance types.
CJE now supports mount options for NFS.
On Red Hat Enterprise Linux and CentOS installations, logstash did not send logs to ElasticSearch. This fix corrects this situation for new installations. Please contact support if you encounter this issue with an existing installation.
Under some circumstances, cluster recovery fails on a CJE anywhere installation. This change addresses these issues.
Upgrading from 1.6.3 to 1.7.0 required manual steps to complete the upgrade. This change automates those steps.
On AWS, after moving a task from one instance to another, various I/O errors can occur, or the volumes of a task can appear mounted multiple times. This change resolves these issues.
When the cluster health was poor, CJE may take more time than necessary to generate the support bundle . This change allows the support bundle to be created more quickly under those conditions.
Under some circumstances, a failure occurs when attempting to produce a support bundle. This change detects the condition and records it.
Prior to this fix, creating a support bundle generated an error if firewalld was not running on CentOS or Red Hat Enterprise Linux.
During installation, a key request to keyserver.ubuntu.com reports a failure. This change resolves this failure.
A CJE Admin can change the JNLP port on the Operations Center UI, however, this is not a best practice as this is set dynamically by CJE on startup.
If you enter an invalid Managed Master image location under the Manage Jenkins page on Operations Center, then 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.
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.
CJE doesn't support installing the Palace Cloud Plugin into masters that are not managed by CloudBees Jenkins Enterprise.
The alert There was an error reporting analytics data links to an invalid URL within the cluster. You can access this by selecting the Manage Jenkins link on the left side of the page.
list-resources operation does not work on OpenStack.
Managed Masters will not be accessible when Operations Center is being upgraded.
Manually stopping a worker instance using AWS are unable to re-join the cluster when restarted. You should use the
cje prepare worker-* operations to change the state of worker instances.
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.
cluster-recover fails 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).
To workaround, and recover in a different availability zone, you will need manually edit the .dna/project.config file and update the "availability_zone" property for each machine instance prior to starting the recovery operation.