CloudBees CI on modern cloud platforms 2.235.2.3

The ServiceNow Plugin is now certified on Orlando, New York, and Madrid versions of ServiceNow.

Support for ElasticSearch 7 was added. Support for ElasticSearch 5 was dropped because it its end-of-life status.

To improve the user experience for users configuring their Slack and GitHub settings, we made various updates to the Personalized Slack Messaging feature, including adding a separate page for a user to configure themselves.

To make more informed improvements to the Personalized Slack Messaging feature, we are now collecting data on the following:

We added a couple of plugins to CAP that were dependencies for the Slack/SCM app integrations including:

Before, if a Managed Master was using hibernation, then it could happen that after a build the links to CloudBees CI shown in the GitHub pull request (PR) could point to a master which had since hibernated, leading to 503 errors.

Before, if a Managed Master was using hibernation, then it could happen that after a build the links to CloudBees CI shown in the GitHub pull request (PR) could point to a master which had since hibernated, leading to 503 errors.

Before, to enable GitHub Checks, users had to create a GitHub App manually, which was tedious and error-prone.

The CloudBees GitHub Reporting feature now supports Bitbucket as an SCM option and has been renamed to CloudBees SCM Reporting.

When using the GitHub App creation wizard to configure CloudBees SCM Reporting, even if CloudBees CI already has a webhook secret registered, the wizard can add another secret.

Before, it was hard to tell from feedback messages what version of the CloudBees SCM Reporting plugin was being run.

With this release we have moved management links to the correct category under Manage Jenkins.

The outdated OkHttp3 v2.7.5 library does not support modern features including TLS 1.3.

In Kubernetes 1.14+, the "OS" node label changed from beta.kubernetes.io/os to kubernetes.io/os. The Kubernetes Plugin tries to ensure that default Pod Templates run on Linux by applying a nodeSelector with the Linux OS label. If the label applied by the Kubernetes Plugin does not match the label in the Kubernetes cluster, the Pod will not be scheduled due to a nodeSelector label mismatch.

When the certificate used to secure the communications to sidecar injector expired, there was no mechanism to renew it and the sidecar injector was no longer usable.

When using the OperationsCenter.RunAsUser attribute in a values.yaml file, the template evaluation fails with an error about incompatible types.

The Service CA bundle is now included. It enhances security when accessing sidecar injector on OpenShift by relying on the Service CA available in the platform.

When recreating a master with the same name as before, the configuration-as-code bundle needs to be updated, but Operations Center is missing the corresponding permissions.

When restarting a master, sometimes the associated service and/or ingress disappears.

A regression in KubectlBuildWrapper prevented its usage.

The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __builtin_darn intrinsic into a single call, thus reducing the entropy of the random number generator. This occurred because a volatile operation was not specified.

A potential security leak existed due to the HTTP method not being required.

CloudBees CI on modern cloud platforms and CloudBees Jenkins Enterprise operations center images included the Mock Security Realm plugin, which is not intended for production usage, only exploration.

We now prevent errors with Personalized Slack Messaging if the Jenkins Root URL is not configured when the a Slack message is created.

We created a safety check for the metrics we collect on SCM/Slack app integrations to be sent only if the queue and sender are initialized and ready.

Before, when using the GitHub Checks tab, lengthy submissions such as from verbose test runs could exceed a GitHub limit and fail to notify anything at all (seen as an error in the system log).

When not using a GitHub App and the Checks tab, certain notifications could attempt to use a long description text that GitHub would reject, leading to a warning in the CloudBees CI system log and a missing notification.

Before, code blocks in the Checks tab coming from build results could have rendered emojis.

Before, when creating a new GitHub App by wizard, the state passed between CloudBees CI and GitHub used encrypted information about CloudBees CI, which was unnecessary.

Before, when a Pipeline step which failed a build had a multiline argument, which is common for example for sh steps, the summary in the Checks tab would be improperly formatted.

Since 2.222.1.1, the security settings enforced by operations center to Client Masters appeared as editable in the masters (Global Security configuration), but any change on them was not saved.

Configuration as Code bundle export was returning "application/json" as the media type; however, the content is YAML syntax. As there is no official IETF media type for YAML, this endpoint now returns "text/plain".

Traversing a Pipeline execution using the FlowGraphTable API (used primarily for the Pipeline Steps view) could cause infinite loops for corrupted Pipelines in rare cases.

Configuration as Code for Masters cannot download plugins if they are under a proxy.