CloudBees Jenkins Platform 2.164.3.2

3 minute read

RELEASED: Public: 2019-05-08

Based on Jenkins LTS2.164.3-cb-2

Rolling release

New features

None

Resolved issues

The license expiration date in the about.md file was set to the JVM locale. The expiration date is now displayed using the UTC format.

The BitBucket and GitHub Branch Source plugin "Checkout over SSH" falls back to using HTTPS when configured to use key on the agent. Now, the "Checkout over SSH" properly accepts and uses key on agent when configured.

  • Fixed "Checkout over SSH" falls back to HTTPS issue

    The BitBucket and GitHub Branch Source plugin "Checkout over SSH" falls back to using HTTPS when configured to use key on the agent. Now, the "Checkout over SSH" properly accepts and uses key on agent when configured.

  • Retry in Declarative options are no longer ignored

    When retry is used as a top-level option in a Declarative Pipeline and a stage fails, the retry attempts will skip all stages due to the original failure. With this fix, the original failure will be reset when the retry begins, allowing stages to execute normally during the retry attempt.

  • Parallel and load steps now clean up internal state correctly

    Users were unable to resume Pipelines that come with nested parallels. Parallel and load steps did not clean up internal state correctly after their executions completed, leading to failures upon resuming a Pipeline and memory leaks in some cases. The internal state of parallel and load steps is now cleaned up correctly when the step completes.

  • Script for Initializing Logstash/Topbeat for Elasticsearch

    A script for initializing Logstash and Topbeat is now available, which allows Elasticsearch to run in workers or controllers.

  • Choice parameter plugin accepts any value when using build step

    Values for choice parameters can be passed via the build step even if those values are not among the allowed values on the target job. The build step will fail with an error if an invalid choice value is specified.

  • Node.js version incompatible with Artifactory past 3.0.0

    Node.js plugin updated to allow installation of Artifactory plugin versions later than 3.0.0.

  • Elasticsearch fails due to excessive snapshot accumulation

    Elasticsearch clusters can fail due to excessive snapshot backup accumulation. A fix is available that limits the number of snapshots.

  • Problem reprovisioning of master due to device lock issues

    A bug has been fixed where a device could not be unmounted due to device locks from open file descriptors or a crashed/hung process, causing manual forced restart of workers.

  • Update Center fix for open source Azure CLI plugin

    The Update Center used to not show the open source Azure CLI plugin due to a conflicting artifactId. For new versions of CloudBees Products, the open source Azure CLI plugin is available in the Update Center. CloudBees Azure CLI plugin has been deprecated and should not be used.

  • Data from the Setup Wizard is sent to Segment

    Sign up information from the Setup Wizard is sent to Segment.

  • Wrong management for plugins with the same ID

When two plugins have the same ID (but different groupIds), the plugin information provided in Plugins Management did not belong to the proper one and updates for the wrong plugin were offered.

Information for both plugins can now be visualized when managing plugins.

  • dna CLI fails with some terminal dimensions

    An update to the dna command fixes a crash when displaying terminal output with unspecified dimensions.

  • Elasticsearch share is mounted on build workers

    A bug has been fixed where Elasticsearch was mounted on build workers, which is unnecessary as Elasticsearch does not run on build workers.

  • Credentials masking works with passwords with special characters

    Credentials masking works even when the password has special characters but does not include a new line. For example, if your secret is an SSH key which takes multiple lines, they might not be detected.

Known issues

  • Pipeline stages, parallels, and step incorrectly marked unstable

    When there is a build with an unstable stage, parallel, or step, all the stages, parallels, and steps are incorrectly marked as unstable instead of just the unstable one that caused the Pipeline to be unstable. This is a known issue in the pipeline-graph-analysis plugin.