JNLP Port is now enforced on startup and cannot be set using UI. The value of the JNLP port is dynamic and located in the 31000-32000 used by Mesos.
This resolves a problem where the
/usr/share/elasticsearch/snapshot is busy or already mounted during
cluster-init causing the
cluster-init operation to fail.
Resolved a problem where certificates are not setup properly on
certificates-update causing failures.
This resolves a mistake where there were duplicate 'scripts' entry in
1.9.0 UPGRADES file.
This was a minor clean-up to remove maven-jdk-7 template which was no longer required.
Update the default memory allocations for CJE Maven Docker Agent Template to provide more appropriate memory sizing.
Resolve an issue where the AdminMonitor for analytics had an invalid URL.
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.
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).
CJE can fail to upgrade when a worker was incompletely set up.
Under some circumstances, a
cje prepare worker-add operation can fail. The typical case (on Amazon) is when the user's MFA code is incorrectly entered when prompted after the "apply" step. This results in a worker that is incompletely set up and the instance isn't started.
When this condition exists, an upgrade will fail.
To resolve this, use the
cje prepare worker-remove on the partially created workers, and then restart the upgrade process.