CloudBees CI on traditional platforms 2.346.3.4

A new Test SSH Connection button was added to the configuration form for both shared and static agents. This button verifies the connection to the agent and validates that the credentials and connection details are correct.

A new table is now available at the controller’s item management page in the operations center. The table displays the historical bundle validation data; validation state, number of errors and warnings, bundle version, and validation date.

A new HTTP endpoint lets you view the validation log in JSON format. The output can be filtered to controllers by specifying the controller id as a simple string or regexp.

A new CLI command lets you view the validation log in JSON format. The output can be filtered by specifying the controller id as a simple string or a regexp.

The Load CasC Bundles left action is not visible if there are no sources of bundles defined or if it is not enabled.

When processing requests for shared agents or shared clouds, CloudBees observed excessive classloading and locking under heavy scale.

A new boolean parameter controller is added to enrich the current JSON result with the controllers` effective validation logs assigned with the bundle.

The new parameter -c is added to enrich the current JSON result with the controllers' effective validation logs assigned with the bundle.

A new update was introduced, allowing you to manually bulk disable agents, when there is a low load, to reduce costs. The new CLI lets you disable agents for particular clouds.

The bundle name is displayed in the first column of the bundle validation log table in the controller > Manage page. If the bundle has changed, you can now see which bundle corresponds to each row.

In this release, some source code was removed in favor of a new API that was introduced in the Pipeline: API plugin. This update reduces technical debt and prevents code duplication.

Fixed size and appearance issues with the Move/Copy/Promote dialog.

The coordinates.json file can become corrupt if a read operation occurs at the same time as a write operation when the plugin catalog defines the plugins that use the URL during low system performance. In these cases, the file is not parsed and this prevents errors.

ComputedFolders now schedule a build when they are newly created or modified in the following relevant fields:

Validation occurs when a bundle is configured through regexp and the raw bundle contains changes.

The left-side action page now captures the possible errors, avoiding the error screen and showing the error details.

CloudBees is addressing all icon compatibility and inconsistency issues with the Jenkins LTS 2.346 upgrade.

The internal testing period is over, the feedback link is no longer required for messages sent to Slack.

If the Controller Bundle Location Service detected a new bundle or a new version of an existing bundle during the start up process, the validation entry was not recorded.

The CloudBees Role-Based Access Control Plugin previously allowed users to configure group role assignments with only the Group/Manage permission when using the REST API or the Jenkins CLI.

When the bundle.yaml file refers files or directories that do not exist, the bundle is duplicating the validation message. If the polling is active, the bundle is always validated and this floods the logs.

A write lock was applied to one of the read operations on a group, causing thread contention issues.

If a NullPointerException is returned during the check for a new bundle version, the error was not properly handled and the Jenkins error page was displayed.

If there is a new available version of a bundle, this bundle is validated. If the new version contains an items.yaml file that configures a GitHub Organization, Bitbucket project, or Multibranch Pipeline, a NullPointerException is returned if the item does not include the disabled property.

If a bundle with more than one Plugin Catalog is stored through the Controller Bundle Location Service, the validation is not executed and the warning message is not displayed.

When a user logs in as the same username with a different case, the User Activity Monitoring Plugin logged two records, even though the user is accessing the same account. This is because usernames are case sensitive.

In version 5.64 of the CloudBees Role-Based Access Control Plugin, the Group#members attribute was split into Group#users and Group#groups attributes.

Some classes were removed from the Kubernetes Plugin, causing the Kube Agent Management Plugin to fail and produce an error.

The offline Update Center can only be updated by upgrading the WAR file and the WAR file is trusted, giving no added security by signing the file that is inside the WAR file. The product might not start up when the certificate that is used to sign the JSON is no longer valid (occurs if the product had not been upgraded in a long time). The JSON embedded inside the WAR file is no longer signed.

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.

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.346 upgrade notes