CloudBees CI on modern cloud platforms 2.568.1.37445

CloudBees CI plugins were previously labeled in the plugin manager with one of three badges: Proprietary (Tier 1), Verified (Tier 1), and Compatible (Tier 2). These have been consolidated into a single Supported badge. Plugins that previously displayed no badge remain unlabeled and are not supported by CloudBees. The setup wizard no longer categorizes plugins individually. If a plugin is shown in the setup wizard, it is supported.

A number of unnecessary or unused plugin dependencies have been removed or made optional to reduce unnecessary coupling between plugins and allow for more flexible installations:

The following plugins have been removed from the operations center CloudBees Assurance Program since 2.555.3.36985:

The following plugins have been removed from the controller CloudBees Assurance Program since 2.555.3.36985:

You can now set custom Google Cloud Platform (GCP) resource labels on provisioned agent VMs. Labels are useful for cost allocation, filtering, and policy enforcement in GCP. Configure via the UI or Configuration as Code. Label values must be single words with no spaces and a maximum of 63 characters; GCP rejects invalid values at instance-creation time.

Previously, if a zone encountered a capacity exhaustion error, the only option was to wait and retry. The Google Compute Engine plugin (google-compute-engine) now supports fallback options when a zone on Google Cloud Platform (GCP) encounters capacity exhaustion, using a zone cooldown period to manage the transition. You can configure the fallbackZones option within an instance configuration to specify fallback zones. Additionally, if multiple instance configurations or clouds are available, the plugin falls back to instance configurations within the same cloud before trying another cloud. Refer to Google Compute Engine: Capacity Fallback for more information.

When the CloudBees Software Delivery Automation Data Plugin (cloudbees-platform-data) is installed on a High Availability (HA) controller, it triggers additional saves of build objects after build completion, causing unnecessary replication traffic. A new administrative monitor now warns you when this plugin is detected and provides an uninstall action. Refer to HA considerations for more information on plugins that are incompatible with HA.

The exportSonarQubeScan Pipeline step now accepts two new optional parameters, branch and pullRequest, allowing you to filter SonarQube issues and hotspots to a specific branch or pull request.

Because Blue Ocean is no longer in the CloudBees Assurance Program, there is no longer a need for a dedicated administrative monitor in High Availability (HA) controllers highlighting that some Blue Ocean functions do not work consistently across replicas. This information remains in the documentation, along with information about other non-CAP plugins.

The streaming pipe buffer used by writeCache has been increased from the previous Java default of 1 KB to 1 MB, so uploads to a Google Cloud Storage backend are no longer limited by the producer-to-consumer handoff, closing the ~2x gap with the native gcloud CLI. You can increase the pipe buffer size using the com.cloudbees.cache.compatibility.S3CompatibleCacheWriter.PIPE_BUFFER_SIZE_BYTES system property.

The CloudBees License Tracker plugin (cloudbees-license-tracker) now uses the Jenkins HTTP proxy configuration when sending User License Counting (ULC) telemetry data to Segment.

Previously, the Roles  Who am I? page did not display group membership for the signed-in user. Group membership now displays correctly.

Enabling attachBuildLog on builds with large console output no longer causes an OutOfMemoryError.

A number of plugins which solely provided APIs to other plugins were incorrectly listed as mandatory in the plugin lists for operations center and/or controllers when the usages were solely in optional plugins. The API plugins themselves have now been made optional, so they will not be installed in new servers unless requested by another plugin. If unused, they can be uninstalled.

In certain cases, the setup wizard offers plugins which were defined in bootstrap scope for the server, meaning they were already installed by the time the setup wizard ran, so it was misleading to then offer to install them. In other cases, plugins which are used solely as APIs for other plugins were offered; these will be installed if, and only if, certain plugins are selected for installation.

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.