CloudBees CI on modern cloud platforms 2.401.3.3

The following plugins have been added to the Controller CloudBees Assurance Program since 2.401.2.3:

CloudBees introduces Workspace Caching with (AWS) S3 that allows pipelines caching artifacts on AWS S3 and using them for upcoming builds.

The CloudBees Build Strategies plugin is a new CloudBees Assurance Program (CAP) plugin.

CloudBees Pipeline Explorer is now a CloudBees Assurance Program (CAP) plugin. It is not installed automatically when upgrading, but it will install as a suggested plugin for new controllers. After it is installed, it is enabled by default.

Configuration as Code validations and prevalidations now come with the full list of validations that are performed as INFO messages. These messages will be available in bundle update logs, bundle update screen, controller configuration page, as well as CLI and endpoints.

All YAML files in a bundle can now be validated against their schema, and the syntactic error information is also provided.

When a controller has allowExternalAgents set, status.hostIP is now added as JNLP_NODE_IP.

Despite a warning in the UI, when configuring a Managed controller, it is possible to choose the same domain for different managed controllers. That is a valid use case in environments where multiple Kubernetes endpoints are needed (such as a multi-cluster environment). However, this can cause unexpected behavior as managed controllers are sometimes searched for only by their domain, especially when using the hibernation feature. This issue has been fixed.

When the Controller CasC Bundle Location is configured to check out the bundles from a Git repository and the branches are named following the Gitflow pattern, such as feature/dev, bundles from those branches are marked as duplicated.

When a CasC-created shared agent item is configured with the retention strategy ALWAYS and the ‘sharedSlavePropertyImpl` property is added to the item in items.yaml, the shared agent no longer fails when the connection is set.

After checking out the CasC Controller Bundles in the Operations Center, validations take a long time to execute, causing a timeout when the number of controllers is high.

controller will now start normally, ignoring the file in the URL if it’s in the same version.

When installing a plugin that is not in the CloudBees Assurance Program, which provides new credential type(s) in a client controller (for example, Azure VM Cloud, HashiCorp Vault plugin), looking up such credentials failed with an exception.

In the Pipeline Explorer, the CLI commands apply-skip and remove-skip cannot be used with Pipeline jobs. This issue is now fixed.

The cluster operations step Execute Groovy Script on Controller was still explicitly requiring the deprecated Overall/RunScripts permission (in addition to Overall/Administer) that is deprecated. This issue is now fixed. The step now only requires the Overall/Administer permission.

There was an error with in-progress pipelines that have nested parallel steps so that some stages appear more than once. This is now fixed.

When the user tries to check the single sign-on (SSO) configuration with CloudBees Software Delivery Automation, it would fail with a 302 status code. A different URL is used for verification which returns 200 (when the SDA URL is correct).

The System Configuration screen’s text field for "Send analytics events to this URL" showed a 401 status code even when the authentication was correct. The check is now authenticated.

The anonymization slows down the generation of a Support Bundle and has a noticeable impact on performance, especially on larger instances. The general issue has been fixed. The slowness and the resource consumption has improved, allowing even larger instances to benefit from the feature.

There was a syntax error in the sidecar-injector Helm template helpers. This issue is resolved.

If a plugin that provides an alternate Notification URL is only installed on the controller, but not on the operations center; then the Users' Notification URLs that are set on controllers with values provided by that plugin could be reset after synchronization with the operations center.

There was an issue with the controller permissions gathering tasks in the operations center (those are permissions defined by plugins that are installed in controllers but not in the operations center).

The licenses for cloudbees-analytics contained an incorrect URL for the cloudbees-analytics-api library. As the API has no project page, the URL has been removed.

The 404 error was caused by a dead link.

JENKINS-71466: Support Bundle generation returns 'MalformedInputException: Input length = 1' when anonymization is on. Generate a support bundle with the Controller Task Log Recorders option.

Because of known issues in the Java HTTP Client, there could be performance issues in Operations Center to Controllers interactions in heavily loaded environments.

When the operations center sends new bundle versions to controllers older than 2.401.1.3, the controller cannot start.

If a Pipeline Template Catalog is configured in the CasC jenkins.yaml file and the id property is not defined, the catalog is duplicated on each instance restart and in the exported CasC configuration.

When searching for a specific plugin under 'Available' tab in operations center Plugin Manager, the search results shows duplicate entries of the searched plugin.