CloudBees CI on traditional platforms 2.332.2.4

Previously released as a Preview feature, CasC for the operations center is now fully supported. This allows you to capture the configuration of the operations center in human-readable declarative files that can be used in a reproducible way and eliminates the need for additional tools or custom scripts that must be manually maintained.

Previously released as a Preview feature, the Configuration as Code bundle location setting is now fully supported. It allows you to configure a local folder on the operations center server or an SCM repository for adding controller CasC bundles to the operations center’s internal storage.

Previously released as a Preview feature, the creation of various items using the operations center and controller `items.yaml' file is now fully supported. When these items are created in an instance, it is possible to export their configuration in a YAML format that can be used to create and configure the items using CasC.

When a bundle is added to the operations center using the Configuration as Code bundle location, it can be validated using a new HTTP endpoint.

When a bundle is added to the operations center using the Configuration as Code bundle location, it can be validated by using a new CLI command.

There have been improvements made to the validation error and warning messages.

Credentials can now be exported and defined as part of the folder-based items in the items.yaml files of the CasC bundles.

The variables that are defined in the configuration bundles are now exposed in the jenkins.yaml, items.yaml, and rbac.yaml files.

The JCasC variables format is now supported in the items and rbac sections of the configuration bundles.

A new section that defines the variables is now available in the configuration bundle under the variables section name.

When multiple plugin catalog files are in a bundle, a log message is generated to identify which file is effectively used.

The rbac.yaml file in the CasC bundle is now validated to verify the following:

The version of Woodstox that was used in the SAML plugin contained an injection flaw that could cause issues during the parsing of XML data.

The last update date function was not working when you clicked the Check now button in the controller plugin management options.

The connection was not closing properly when querying for security warnings.

When adding groups as members of an RBAC group, the autocompletion feature only worked for groups that were defined in the root of the current controller.

Frequent calls to the Jenkins method Queue.maintain() could have a negative impact on performance. Occasionally, the number of calls resulted in poor instance health and connection issues that could only be resolved by restarting the controller.

CloudBees is updating terminology to remove offensive text. During this ongoing initiative, “controller” replaces “master,” “agent” replaces “slave,” “allowlist” replaces “whitelist,” and “denylist” replaces “blacklist.”

There were instances of file locks that could cause failures in certain use cases when you run a controller in a Windows environment.

Some code was duplicated from Jenkins core into the proprietary plugin.

To avoid version conflicts with other components in CloudBees CI, the High Availability plugin now shades its dependencies.

In the definition of an item in the items.yaml file, if a property that was expected by the constructor was missing, a NullPointerException was returned. For example, there is a missing scope in a credential definition.

When bundles were loaded, the bundle synchronization was missing the bundle descriptor validator that checks the mandatory fields and sections information.

Some anonymous classes were not considered as enumerations during the items creation with CasC.

When an item in the items.yaml file has a property that receives an enumeration class in its constructor, the value was not cast to the proper type, and an exception was returned.

If controller bundles are synchronized in the operations center using a Freestyle job with the Synchronize bundles from workspace with internal storage build step, the bundles were not validated.

In the bundle.yaml file, when a folder was referenced with files instead of the list of files, a warning message was displayed that states the files in that folder are not referenced.

If the CasC bundle.yaml file specified a subfolder instead of the list of files within the subfolder and one of those files within the folder was changed, the change was not propagated and the new version of the bundle was not available to the controllers.

The SCMSources array was incorrectly being exported with the Organization Folder during a CasC export.

If the CasC rbac.yaml file did not include a roles section, the authenticated role was incorrectly initialized with the Overall/Read permission granted.

When you exported a parameterized Pipeline, the parameterDefinitionNames property was exported as part of the parameter definitions. If the exported item was imported later, an error occurred.

The icon paths have been updated and the issue has been resolved.

The inline help for the withEnv step was updated to show that the environment variable keys are case insensitive, but they do preserve the case.

Plugins that were disabled were displayed as blank lines in the CloudBees Plugin Usage Analyzer report.

The Jenkins community will begin supporting Java 11-specific features soon (Java 11 byte code), at which point it will no longer be possible to 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.

The minimum required Jenkins version was updated to the latest LTS, version 2.332.1.

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.

Jenkins 2.326 removes the ability to disable or customize the agent-to-controller-security system. The following plugins are known to be affected by this change:

Version 3.0 of the Matrix Authorization Strategy plugin extends the formats for permission assignments both internally and when used with the Job DSL and Configuration as Code plugins. With the upgrade to version 3.0, all past permission assignments are now considered ambiguous. While existing configurations can still be read, if the permission assignment configurations contain ambiguous entries, warnings will appear in the UI and in logs.