CloudBees CI on traditional platforms 2.568.3.37907

Jenkins core is dropping the commons-lang2 library, which is no longer supported. The Swarm plugin (swarm) and Parameterized Scheduler plugin (parameterized-scheduler) have a dependency on it; if you use either plugin, manually upgrade them to the following versions before upgrading your CloudBees CI High Availability (HA) controller:

The following plugins have been added to the operations center CloudBees Assurance Program since 2.568.2.37664:

The following plugins have been added to the controller CloudBees Assurance Program since 2.568.2.37664:

UI controls used to select local or remote folders or items have been simplified to plain text fields with completion and validation, reducing complexity and more closely aligning with Configuration as Code (CasC), REST, and CLI usage. This includes the target folder selection for Move/Copy/Promote, the source job for copy remote artifact, and the target job for trigger remote build. For build steps, configuration is done through the UI for Freestyle projects and through the Pipeline Syntax tool for Pipeline projects. cjp-protocol URLs are now also supported and properly retained when saving configurations.

The badge on the Related builds panel in CloudBees Pipeline Explorer now uses a neutral gray color instead of orange, which previously suggested an error or warning state.

In CasC, bundles can reference entire directories instead of listing individual YAML files. Previously, the bundle validation endpoint incorrectly reported these bundles as invalid when a directory was referenced in the rbac, items, or plugins sections of the bundle.yaml file, even though the bundles loaded correctly at runtime. Bundle validation now correctly handles directory references across all supported bundle sections.

When a Configuration as Code (CasC) bundle’s jcasc section listed more than one entry where at least one entry was a directory, only the first entry was applied to the controller. All remaining entries, whether a second directory or a standalone file, were silently ignored with no error or warning. This has been resolved; all jcasc entries in a bundle are now applied correctly.

Previously, when the operations center was configured with controllers running on a secondary Kubernetes cluster, startup could stall or hang for several minutes while applying its CasC bundle if that cluster was temporarily unreachable or experiencing network issues. Startup now continues normally even when a controller’s cluster cannot be reached; any pending disk-resize checks for those controllers run in the background and no longer block the operations center from coming online.

Local group definitions in a controller CasC bundle items.yaml file can refer to service account members defined in the operations center (typically in the operations center rbac.yaml file) when using single sign-on (SSO) with managed authorization. However, validation checking whether the service account name existed could have failed when the controller first started up, before it had connected to the operations center to synchronize its root RBAC configuration. Validation of global service account names is now skipped when applied from a CasC bundle.

vaultGithubApp credentials provided by the CloudBees HashiCorp Vault plugin (cloudbees-hashicorp-vault) could become unusable after a Jenkins restart, causing operations that rely on them (such as Multibranch Pipeline or Organization Folder scans and connection tests) to fail with a NullPointerException. This occurred because the credential type extends the GitHub App credentials from the open-source GitHub Branch Source plugin (github-branch-source), whose deserialization logic did not re-initialize the required internal state for a subclass. The deserialization logic has been updated to correctly initialize the required state. As a temporary workaround for previous versions, saving the affected credential again restores it until the next restart.

When an HA controller generated a support bundle with extremely large log files, some entries could be lost and their content replaced with errors. This occurred because temporary files were deleted if adding them to the support bundle .zip file took more than one minute. This timeout could be exceeded when using log file aggregation mode (the default) or when other large files were included. Temporary files are now deleted immediately after they are read, regardless of how long the read takes.

A regression in the CloudBees Quiet Start plugin (cloudbees-quiet-start) caused the Stay in "quieting down" state when restarted checkbox to have no effect, starting the controller in normal operation mode instead of quieting down mode upon restart. This allowed builds to run immediately on controller start, contrary to the expected behavior. When Stay in "quieting down" state when restarted is selected, the controller now correctly starts in quieting down mode, preventing builds from running immediately upon restart.

Under certain conditions, the Role-Based Access Control (RBAC) Groups page or its permission table could appear empty. Rendering of the RBAC Groups page has been improved to handle these cases correctly.

The Pipeline Event Step plugin (pipeline-event-step) included HTML help files that worked for inline display in the Snippet Generator but broke rendering of the Steps Reference. This has been resolved; Steps Reference now renders correctly when the plugin is installed.

When configuring a skip group, the Includes and Excludes fields accept either an Ant-style pattern like deploy/* or a blank value. A literal name like deploy/main with no wildcards was valid but triggered a form validation error. Form validation has been removed from these fields, as there are no clearly invalid values.

When using unclassified.skipGroup.skipGroups in jenkins.yaml, edits to until did not take effect when applying revised CasC bundles unless other skip group fields (such as description) were also modified. The until field now updates correctly when a CasC bundle is applied.

When you search for a specific plugin under the Available tab in the Operations center Plugin Manager, the search results show duplicate entries for the plugin.