CJE 1.6.3 requires the LBaaS v2 API when running on OpenStack. Prior versions required LBaaS v1 API.
This feature allows users to define instance tags for AWS and OpenStack resources in cluster-init and worker-add operations. This feature adds the
resource_tags parameter to cluster-init and worker-add.
CJE 1.6.3 adds cluster outbound IPv6 support on AWS. This allows CJE to support external services that are reachable via IPv6.
This feature enables direct connections to Jenkins sshd server when using
jenkins-cli.jar. Users can now use Jenkins cli commands from within CJE.
Before this change, CJE Anywhere installation failed if the machine instances are using LDAP for account management. This change checks for the existence of user accounts using a more reliable method.
Prior versions of CJE had a bug where AWS resources were created before confirming that the relevant resources were available. This led to a partial cluster creation state and the user had to destroy the cluster and start over. This issue has now been fixed in the current version
This change clarifies the worker state information for the list-workers operation. Previously a worker was labeled as "ACTIVE" which wasn't always correct. Now workers are marked as "ENABLED" to better reflect the known state.
In prior versions of CJE, an ElasticSearch Worker VM could lose its snapshot mount after a reboot. This change ensures that s3fs mount occurs correctly.
The ElasticSearch file system mounts are not required on build workers. This change removes the unnecessary mount.
In prior releases, creating a support bundle could fail if CJE couldn't connect to the docker daemon. With this change, the support bundle creation proceeds correctly.
Prior to this change, security groups were not updated if they changed after a cluster-init failure. With this change, the security group changes are applied correctly.
Before this change, a user could stop the entire cluster using a command such as
cje run stop x. This change prevents this unintended result.
In prior versions, under some circumstances, CJE would launch too many
docker-clean containers operations. This change eliminates the excess launches.
In prior versions of CJE, support bundle creation could fail if the content of 'docker.tar.gz' had restricted permissions. This change ensures that CJE creates the support bundle correctly.
In prior releases, the command
cje status shows a stack trace if a worker was down.
In previous releases, the
cje status command returns
OK even if Operations Center is unreachable. With this change, the status command shows the correct status of the Operations Center.
Fixes the issue where Mesos log rotation was not working on Workers
Docker configuration is not set in controllers in AWS
Security Advisory related to the
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 CJOC, 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 CJE
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.
Masters will not be accessible when CJOC is being upgraded