With this enhancement, CJE would allow customers to use custom hosted zones that would enable better control for routing traffic inside a VPC.
When using Identity v3, either a domain id or a domain name must be provided when logging in. For some customers it may be easier to handle domain name directly because domain id is a uuid that is not user-facing.
Disable terraform version check to avoid installation or upgrade delays in "firewalled" environments
Add support for ipv6 ingress on AWS.
This fix makes it easier for users to pull logs from specific docker containers and add it to a support bundle, if required.
Improve docker cleanup. It is now based on
spotify/docker-gc that optimizes the removal of tagged docker images.
Preliminary support of self-signed certificates has been implemented. Full support requires an upgrade of
master-provisioning plugins which will be available later.
This fix improves the reliability of NFS checks while installing a CJE cluster with an NFS storage backend
cje check operation can be run to ensure a CJE cluster has been installed correctly. This ticket fixes an issue that caused the operation to fail.
Handles index restore failures during elasticsearch-restore operation more gracefully. If an index restore fails, it will be skipped but it won't prevent other indexes to be restored.
Fixed typo in cluster-init input file.
Logstash was not sending logs to ElasticSearch after a RedHat Enterprise Linux or CentOS upgrade. This change resolves this issue.
list-resources operation wasn't displaying newly added Workers if the
internal=yes config was set in the
CJE, when installed using NFS 4.x servers as a storage solution, will not properly mount
JENKINS_HOME in containers used by CJE. This issue could lead to installation failures. This issue only applies to installations on OpenStack and vSphere.
Before starting an install or upgrade using an NFS 4.x server, please contact your CloudBees support representative for details on how to adjust the configuration to ensure that it works properly.
The CloudBees team will provide the resolution to this issue in the upcoming release
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, 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.
The list-resources operation does not work on OpenStack.
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.
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.
With the i3 family of EC2 computes, the
instance_storage type is not being leveraged by CJE