|CloudBees will no longer be supporting CloudBees Jenkins Enterprise 1.x after July 30, 2020. This end-of-life announcement allows CloudBees to focus on driving new technology and product innovation for CloudBees CI. For information on moving to CloudBees CI, please refer to CloudBees Jenkins Enterprise 1.x to CloudBees CI on modern cloud platforms migration guide which has been created to help you with the migration process. Existing customers can also contact their CSM to help ensure a smooth transition.|
RELEASED: Public: 2017-03-31
Based on Jenkins LTS
CloudBees Internal Ticket: [TIGER-2430]
CJE now confirms that a worker is not already part of the cluster before adding it.
CloudBees Internal Ticket: [TIGER-2118]
Allow creation of a support bundle with an ongoing CLI operation.
CloudBees Internal Ticket: [TIGER-2640]
The support bundle could not include syslogs under certain circumstances. The support bundle now correctly retrieves syslogs.
CloudBees Internal Ticket: [TIGER-2614]
Ensure that ElasticSearch does not run on dedicated build workers, and thus improving the performance of the jobs/pipelines running on those build workers
CloudBees Internal Ticket: [TIGER-2610]
The domain-name-change operation previously required manual intervention to complete. This change fixes the 'domain-name-change' operation such that no manual intervention is required
CloudBees Internal Ticket: [TIGER-2559]
If a volume isn’t sized sufficiently, CJE encountered reliability issues as a side effect of the process of resizing a volume. This fix corrects the resizing process for EBS volumes.
CloudBees Internal Ticket: [TIGER-2531]
Ensure that Docker pipeline works out of the box in the Docker agent definition.
CloudBees Internal Ticket: [TIGER-2463]
Fix an upgrade problem when the cluster has some deleted workers.
CloudBees Internal Ticket: [TIGER-2462]
Improve reliability of Support Bundle operation.
CloudBees Internal Ticket: [TIGER-2419]
Nginx access log now show real client IP allowing CJE Admins to diagnose the internal routing issues more accurately
CloudBees Internal Ticket: [TIGER-2340]
Ensure that Zookeeper logs to /var/log/zookeeper on all platforms.
CloudBees Internal Ticket: [TIGER-2257]
Outgoing traffic via UDP port 53 is now permitted in user-provided VPC environment.
CloudBees Internal Ticket: [TIGER-1693]
Ensure credential files are protected with correct permission settings.
CloudBees Internal Ticket: [TIGER-2729]
OpenStack is not a supported distribution for
1.6.2. We are urging customers to instead use
1.6.3when it is released due to the support of v2 load balancers and the complexity of upgrading from v1 to v2 for OpenStack LBaaS.
CloudBees Internal Ticket: [TIGER-2321]
Despite the UI allows to change the JNLP port, it shouldn’t be done as this is set dynamically by CJE on startup.
CloudBees Internal Ticket: [TIGER-2355]
If you enter an invalid Managed Master image location under the "manage" 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.
CloudBees Internal Ticket: [TIGER-2371]
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.
CloudBees Internal Ticket: [TIGER-2426]
CJE doesn’t support installing the Palace Cloud Plugin into masters that are not managed by CJE.
CloudBees Internal Ticket: [TIGER-2427]
When using the operation cluster-recover, it is simpler to keep the cluster in the same AWS availability zone (AZ).
CloudBees Internal Ticket: [TIGER-2459]
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.
CloudBees Internal Ticket: [TIGER-2466]
Under certain circumstances, the mesos-slave process can fail to start. When this occurs, it will be impossible for mesos to start processes and containers on that worker.
You can confirm this by ssh-ing into a shell running on the affected worker and running this command
sudo service mesos-slave status
To resolve this, use these commands in a shell window connected to the affected worker:
sudo rm -r /var/lib/mesos/meta/ sudo service mesos-slave restart
CloudBees Internal Ticket: [TIGER-2692]
The 'list-resources' operation does not work properly on OpenStack.
CloudBees Internal Ticket: [TIGER-2662]
Quoted arguments not handled correctly in CJE CLI.
CloudBees Internal Ticket: [TIGER-2522]
Masters may go off-line during CJOC upgrade.