CloudBees CI release highlights
What’s new in CloudBees CI 2.346.2.2
- New Validation Log page displays the status of invalid bundles (BEE-10555)
A new page to access the validation records of bundles stored in the operations center is now available.
- New screen shows the differences between the current bundle and a newly available bundle (BEE-15137)
When CloudBees CI detects a new version of the current bundle, the Bundle update tab on the Configuration as Code Bundle page displays a link to a new screen that shows the differences between the current bundle and the new one.
Each section of the bundle now has a tab that lists:
- New HTTP endpoint was added to view the validation log (BEE-10559)
A new HTTP endpoint lets you view the validation log in JSON format. The output can be filtered to a single bundle by specifying the bundle
This endpoint provides the raw bundle, structural validations.
For more information, refer to Configuration as Code (CasC) HTTP API.
- New CLI command added to view the validation log (BEE-10558)
A new CLI command lets you view the validation log in JSON format. You can filter the output to a single bundle by specifying the bundle
This CLI provides the raw bundle, structural validations.
For more information, refer to Configuration as Code (CasC) CLI.
- Only sections with changes are reloaded from the new bundle version (BEE-15460)
When you click the Reload Configuration button on the Bundle update tab of the CloudBees Configuration as Code export and update page, only the sections with changes are reloaded.
If there are any
variable.yamlfiles that have changes, a partial reload is not possible, and a full reload is performed.
For more information, refer to the following topics:
- Validations on effective bundles were not shown in the administrative monitor (BEE-10554)
Now validations performed by controllers over provided effective bundles are also shown in the administrative monitor when there are errors or warnings.
- Split RBAC and Item initialization into separate processes (BEE-19521)
The initialization of RBAC and Items has been split into two separate processes to allow new bundle versions to be partially reloaded.
- Allow enabling Beekeeper plugin exceptions from the CasC bundle (BEE-14986)
Previously, you could only create Beekeeper plugin exceptions by explicitly configuring them on each controller from the operations center.
Now, you can activate Beekeeper plugin exceptions on a given controller by using the
allowCapExceptionsflag in the bundle descriptor.
- Updated the icons in the CasC plugins (BEE-19561)
Replaced the outdated CloudBees icons with updated menu icons.
- User interface (UI) updates (BEE-19328, BEE-19558, BEE-19560, BEE-19986)
CloudBees is addressing all icon compatibility and inconsistency issues with the Jenkins LTS 2.346 upgrade.
- Fixed checkpoint compatibility issues (BEE-18935)
When you used the updated versions of some open-source Pipeline plugins, the checkpoint step did not properly resume from the checkpoint.
This issue has been resolved.
- The Kubernetes property`kubernetesFolderProperty/permittedClouds` does not work with CasC (BEE-16671)
Previously, you could not add permitted clouds via CasC. Using the Kubernetes property
permittedCloudsgenerated a stack trace error.
This issue has been resolved. You can now create or update permitted clouds using CasC. Additionally, a UI issue that required you to save a folder configuration twice before being able to configure it has been resolved. Permitted clouds can now be configured directly, using either the UI or CasC.
- Updated the UI (BEE-19328)
UI consistency issues with Jenkins LTS 2.346 were resolved.
- Pipelines that used the
envstep returned an error when they resumed (BEE-19367)
envstep was improperly deserializing when Pipelines resumed.
This issue has been resolved.
- Jenkins logs are not appended to the service log file in an RPM installation that uses Java 8 (BEE-20636)
If you use an RPM to upgrade the product while using Java 8, the Jenkins logs are no longer appended to the following configured service log by default:
You should migrate to Java 11 to resolve this issue. For more information, refer to Migrating to Java 11.
- Duplicate Pipeline Template Catalogs in the Configuration as Code (CasC) for Controllers
jenkins.yamlfile on each instance restart (BEE-12722)
If a Pipeline Template Catalog is configured in the CasC
jenkins.yamlfile and the
idproperty is not defined, the catalog is duplicated on each instance restart and in the exported CasC configuration.
- Jobs based on templates are not created using the correct template (BEE-19032)
When a job based on a template is created using CasC, the template used is a random one of the same type instead of the one that was selected.
- The CasC bundles synchronization step will be deprecated in February 2023 (BEE-17915)
A message about the step deprecation appears in every job’s execution logs and also on the configuration screen when a new job is defined.
- Migration to Java 11 will soon be required for new releases (BEE-42)
The Jenkins community will support Java 11-specific features soon (Java 11 byte code) and then you cannot use a Java 8 runtime environment. Because CloudBees CI on traditional platforms is based on the Jenkins LTS, future releases of CloudBees CI on traditional platforms will have the same requirement.
CloudBees strongly recommends that you upgrade your CloudBees CI on traditional platforms environment to run Java 11 as soon as possible. Some of the Java 11 updates may require action on your part, and there may be a specific order in which you should upgrade components in your environment. For more information, refer to Migrating to Java 11.
- When you upgrade to Java 11, you must update your Java garbage collection arguments (BEE-16018)
Garbage collection has been updated in Java 11. Many of the previously recommended arguments are no longer supported. When you upgrade your JDK to Java 11, you must also update your garbage collection configuration. Using unsupported Java arguments will result in startup failure.
For more information, refer to Adding Java arguments to the Jenkins service configuration file.
- Jenkins upgrade notes