CloudBees CI on modern cloud platforms 2.479.2.3

By default, CloudBees CI uses CloudBees Update Centers during the installation of plugins in Configuration as Code (CasC). Now, if the bundle is using the new CasC Plugin Management (apiVersion: 2 in the bundle.yaml file), you can define a mirror server where the plugins and the Update Center JSON file can be downloaded and used instead. For more information, refer to Create an alternate plugin download site.

The commonly used JAR files used by Kubernetes agents are now directly built in the container image. This results in the faster initialization of Kubernetes agents and the reduction of the load on controllers.

Starting with the 2.414.2.2 release (September 2023) that introduced High Availability (HA), all managed controllers (High Availability (HA) or otherwise) in a Modern installation were started with the jenkins.plugins.git.AbstractGitSCMSource.cacheRootDir and org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheRootDir system properties set to a temporary directory under /tmp/jenkins. Traditional installations were also required to set these properties to a per-replica temporary directory. This prevented clashes between replicas that try to use the same cache directory at the same time. Since library checkouts defaulted to a location in $JENKINS_HOME for the same reason that High Availability (HA) controllers were required to use “clone” mode for libraries (enforced with an administrative monitor), the library caching system was not available and non-multibranch Pipeline projects loading the script from SCM with “lightweight mode” disabled were not safe to use in a High Availability (HA) controller.

The managed controller Hibernation Monitor will use the CloudBees CI container’s startup probe to determine the wake-up timeout threshold. It calculates the wake-up threshold accordingly. If the startup probe is not available, the monitor falls back on the readiness probe to establish the threshold.

The GitHub credentials defined through the CloudBees HashiCorp Vault Plugin introduced a challenge where Configuration as Code exports failed. This issue arises when the plugin interacts with the GitHub credentials stored in HashiCorp Vault, affecting the seamless functionality of Configuration as Code.

Several UI design issues like font sizes, weights, and so on, have been updated to comply with the design guidelines.

The GitHub checks activated checkbox was selected even when GitHub was not selected as the SCM tool. This issue has been resolved.

Support for the Integer version type in the Configuration as Code bundle.yaml file has been updated.

The Dismiss button to dismiss a warning message from the administrative monitor was behind the message itself and could not be selected. This has been fixed so that users can now select the Dismiss button and dismiss a warning message they no longer wish to see.

The Test connection button under Vault authentications Folder Property throws an error when configuring a folder.

The operations center credentials cache file is excluded from the support bundles when the "Other Jenkins configuration files" component is included. This matches what is already done for the main credentials configuration file.

The CloudBees Restricted Credentials plugin reloaded all restricted credentials from disk whenever a credential was retrieved. This caused poor performance of credentials lookups when many restricted credentials were configured.

The CloudBees Hashicorp Vault plugin reloaded all of the Vault credentials from disk whenever a credential was retrieved, causing poor performance of credentials lookups when many Vault credentials were configured.

There was an unexpected line break introduced in the product name in the title bar. This is now fixed.

If there are highly secured environments where only sandbox scripts are allowed, the new Force the use of the sandbox globally in the system security option allows you to force the use of the sandbox globally in the system.

When you try to add a CyberArk credential or Hashicorp Vault credential from the Add button of a credentials form, it fails with the error Domain is read-only and the credential is not created.

In a disaster recovery scenario, when a controller is restored from backup/snapshots in a different cluster, the expectation is that any builds using Kubernetes agents at the time of snapshot should automatically retry the stage when using the "kubernetesAgent()" condition. This logic was incorrect in this scenario, and the build failed to resume, claiming no termination reasons for the agent pod. Now, an empty list of termination reasons, normal behavior when there is no record of the pod’s existence in the new cluster, will qualify for a retry.

In some disaster recovery restore cases that have with an inconsistent filesystem backup, a Pipeline build might detect that an agent it used in the original cluster is missing, but fails to cleanly abort the corresponding node step and let any enclosing retry step take over. This logic has been made more resilient.

In a High Availability (HA) controller, the fix event handling of a new node is declared in a Configuration as Code bundle.

The Maven dependency listing was empty due to a missing integration. Now, the Mavenized dependencies tab displays the correct information.

When using the Hashicorp Vault Github App Credentials, the build execution sometimes failed when a token refresh is required at the time a remote agent needs it.

The management page for the CloudBees Slack plugin has been updated. The overview page design that failed due to a broken CSS integration has been restored.

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

After upgrading to version 2.462.1.3 or later, authentication to the operations center Configuration as Code Retriever endpoint API at ${OC_URL}/casc-retriever/* fails. This is due to the removal of the authentication method enabled by the attribute .OperationsCenter.CasC.Retriever.secrets.adminPassword.