Now includes iPerf3 for network bandwidth checks.
Reduce the number of ELBs needed by CloudBees Jenkins Enterprise
A new operation
docker-registry-update has been added to change the Docker registry after CloudBees Jenkins Enterprise has been installed.
CloudBees Jenkins Enterprise now allows configuration of AWS ELB in public subnets and instances in private subnets.
An additional security group can now be provided when using user-provided VPC. It will be applied to allow instances in the cluster.
When cluster is recovered ensure that it is recovered in same AZ as it was originally running.
Ensure that S3FS mount of ES snapshot directory works when using AWS keys as credentials.
Fix the default instance size when calling
worker-add to use the same as specified during cluster init.
Fix problem that caused
IsManagedMasterFilter to fail in cluster operations with Operations Center
Cluster-recovery documentation now properly explains how to recover a destroyed cluster.
Significantly reduce size of OpenStack images.
RHEL users upgrading from
1.6.0 will have to provide Red Hat Subscription Manager credentials through
CJE now properly enables "EBS-Optimized" machine instances both when installing the cluster and when adding new workers.
Security Advisory related to the
favorite plugin. If you are using this plugin, please follow the instructions in the Security Advisory to get the fix.
A CJE Admin can change the JNLP port on the CJOC 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
CloudBees Jenkins Enterprise 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 Jenkins Enterprise doesn't support installing the Palace Cloud Plugin into masters that are not managed by CloudBees Jenkins Enterprise
When using the operation cluster-recover, it is simpler to keep the cluster in the same AWS availability zone (AZ)
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 properly on OpenStack.
Managed Masters will not be accessible when Operations Center is being upgraded.
If log files are created rapidly, it is possible to fill local disk space before moved or purged.
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.