October 2020 product highlights

CloudBees CI on modern cloud platforms

The following are highlights of the October 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.

Security advisory

No security advisory with this release.

New features

Integrate Velero with CloudBees CI for backup and restore (CPLT2-5847)

Velero can now be used as an optional tool for backing up and restoring Kubernetes cluster resources.

Support for Network Load Balancer (NLB) (CPLT2-6740)

CloudBees CI on modern cloud platforms now supports the newer Network Load Balancer in addition to the Classic Load Balancer.

Support for Red Hat OpenShift Container Platform (OCP) version 4.5 (CPLT2-6776)

CloudBees CI on modern cloud platforms now supports OCP version 4.5.

See Supported platforms for CloudBees CI on modern cloud platforms for details about all supported platforms.

Feature enhancements

Update source repository for nginx-ingress in Helm chart (CPLT2-6737)

The nginx-ingress Helm chart at stable/nginx-ingress has been deprecated.

CloudBees CI Helm dependencies were updated to use the new ingress-nginx chart museum.

Kube Agent Management plugin (CPLT2-6646)

Analytics are now collected about the usage of this plugin.

Add Pipeline Policies section to the SCM reporting commit status (STICKY-463)

If the CloudBees Pipeline Policies Plugin is installed, users will now see information that includes the applied policies and the violated rules.

Update Pipeline Policies report in Slack message (STICKY-740)

The CloudBees Pipeline Policies report within the CloudBees Slack Integration message now shows information about the applied policy and not only the violated rule.

Improve the observability and error logging of the configuration bundle installation (CTR-2302)

When there is an error during CasC bundle processing, a detailed summary is printed to logs. The summary includes whether the plugin catalog was or was not installed as well as the list of plugins not installed.

We added REST API endpoints and CLI commands for the following CasC actions (CTR-2247)
  • list available bundles in Operations Center

  • regenerate a Configuration as Code (CasC) for Masters bundle token for a specific bundle

  • assign a Master Path to a Configuration as Code (CasC) for Masters bundle

    See CasC API endpoints and CasC CLI commands for more information.

Improve UX of exporting Core CasC bundle(CTR-922)

Users with CloudBees CI masters that have the Configuration as Code (CasC) for Masters plugin installed can now view and export the applicable Configuration as Code (CasC) for Masters bundle, by navigating to Manage Jenkins > Export CloudBees Configuration as Code bundle.

See Exporting a CasC bundle for more information.

Beekeeper plugin exceptions

The following enhancements were made to the Beekeeper plugin exceptions feature:

  • User warned when specific plugins are saved as exceptions (FNDJEN-2409)

    When a plugin catalog containing Beekeeper plugin exceptions is selected on the master configuration page, a warning advising users of the implications associated with Beekeeper plugin exceptions is displayed.

  • Send event when Beekeeper plugin exceptions are enabled or disabled (FNDJEN-2421)

    If the CloudBees Assurance Program is enabled on an instance, CloudBees receives a weekly event to indicate if Beekeeper plugin exceptions were allowed or disallowed on that instance.

New option added to the restore configuration section of Restore/Backup jobs (CTR-2295)(CTR-2501)

CloudBees has added a new option to the restore configuration section of Restore/Backup jobs.

Users can now add a comma-separated list of Ant-style patterns to preserve content in the current JENKINS_HOME directory during the restore process, excluding it from the move operation.

A system property is used to set the list of Ant-style patterns. Users need to add cb.backup.restore.keepFilesPattern to the system properties. For example, -Dcb.backup.restore.keepFilesPattern='.snapshots,**/.snapshots' has to be added to the system properties, to preserve `.snapshots filesystem control files in the $JENKINS_HOME directory during the restore process.

See Restoring from the CloudBees Backup Plugin for more information.

Known issues

Version 4.0 or higher of .NET Framework is required to launch controller or agents on Windows services

Starting from this release, .NET Framework 2.0 doesn’t work for launching CloudBees controller or agents as Windows services. Microsoft.NET Framework 4.0 or above is now required for using the default service management features.

This release also upgrades Windows Service Wrapper (WinSW) from 2.3.0 to 2.9.0 and replaces the bundled binary from .NET Framework 2.0 to 4.0. There are many improvements and fixes in these versions, big thanks to NextTurn and all other contributors. You can find the full WinSW changelog here, just a few highlights important to CloudBees users:

  • Prompt for permission elevation when administrative access is required. Now CloudBees users do not need to run the agent process as Administrator to install the agent as a service from GUI.

  • Enable TLS 1.1/1.2 in .NET Framework 4.0 packages on Windows 7 and Windows Server 2008 R2.

  • Enable strong cryptography when running .NET Framework 4.0 binaries on .NET 4.6.

  • Support security descriptor string in the Windows service definition.

  • Support 'If-Modified-Since' and proxy settings for automatic downloads.

  • Fix Runaway Process Killer extension so that it does not kill wrong processes with the same PID on startup.

  • Fix the default domain name in the serviceaccount parameter (jira:JENKINS-12660[])

  • Fix archiving of old logs in the roll-by-size-time mode.

Use-cases affected by .NET Framework 2.0 support removal

If you use .NET Framework 2.0 to run the CloudBees Windows services, the following use cases are likely to be affected:

  • Installing the CloudBees controller as a Windows service from Web UI. The official MSI Installer supports .NET Framework 2.0 for the moment, but it will be changed in future versions.

  • Installing agents as Windows services from GUI. This feature is provided by the Windows Agent Installer Module from the Jenkins core.

  • Installing agents over Windows Management Instrumentation (WMI) via the WMI Windows Agents plugin

  • Auto-updating of Windows service wrappers on agents installed from GUI.

Upgrade guidelines

If all of your CloudBees controller and agent instances already use .NET Framework 4.0 or above, there are no special upgrade steps required.

If you run the CloudBees controller as a Windows Service with .NET Framework 2.0, this instance will require an upgrade of .NET Framework to version 4.0 or above. .NET Framework 4.6.1 or above is recommended because this .NET version provides many platform features by default (e.g. TLS 1.2 encryption and strong cryptography), and Windows Service Wrapper does not have to apply custom workarounds.

If you want to continue running some of your agents with .NET Framework 2.0, the following extra upgrade steps are required:

  1. Disable auto-upgrade of Windows Service Wrapper on agents by setting the -Dorg.jenkinsci.modules.windows_slave_installer.disableAutoUpdate=true flag on the CloudBees controller side.

  2. Upgrade agents with .NET Framework 4.0+ by downloading the recent Windows Service Wrapper 2.x version from WinSW GitHub Releases and manually replacing the wrapper ".exe" files in the agent workspaces.

CloudBees CI on traditional platforms

The following are highlights of the October 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.

Security advisory

No security advisory with this release.

New features

None.

Feature enhancements

Add Pipeline Policies section to the SCM reporting commit status (STICKY-463)

If the CloudBees Pipeline Policies Plugin is installed, users will now see information that includes the applied policies and the violated rules.

Update Pipeline Policies report in Slack message (STICKY-740)

The CloudBees Pipeline Policies report within the CloudBees Slack Integration message now shows information about the applied policy and not only the violated rule.

Improve the observability and error logging of the configuration bundle installation (CTR-2302)

When there is an error during CasC bundle processing, a detailed summary is printed to logs. The summary includes whether the plugin catalog was or was not installed as well as the list of plugins not installed.

We added REST API endpoints and CLI commands for the following CasC actions (CTR-2247)
  • list available bundles in Operations Center

  • regenerate a Configuration as Code (CasC) for Masters bundle token for a specific bundle

  • assign a Master Path to a Configuration as Code (CasC) for Masters bundle

    See CasC API endpoints and CasC CLI commands for more information.

Improve UX of exporting Core CasC bundle(CTR-922)

Users with CloudBees CI masters that have the Configuration as Code (CasC) for Masters plugin installed can now view and export the applicable Configuration as Code (CasC) for Masters bundle, by navigating to Manage Jenkins > Export CloudBees Configuration as Code bundle.

See Exporting a CasC bundle for more information.

Beekeeper plugin exceptions

The following enhancements were made to the Beekeeper plugin exceptions feature:

  • User warned when specific plugins are saved as exceptions (FNDJEN-2409)

    When a plugin catalog containing Beekeeper plugin exceptions is selected on the master configuration page, a warning advising users of the implications associated with Beekeeper plugin exceptions is displayed.

  • Send event when Beekeeper plugin exceptions are enabled or disabled (FNDJEN-2421)

    If the CloudBees Assurance Program is enabled on an instance, CloudBees receives a weekly event to indicate if Beekeeper plugin exceptions were allowed or disallowed on that instance.

New option added to the restore configuration section of Restore/Backup jobs (CTR-2295)(CTR-2501)

CloudBees has added a new option to the restore configuration section of Restore/Backup jobs.

Users can now add a comma-separated list of Ant-style patterns to preserve content in the current JENKINS_HOME directory during the restore process, excluding it from the move operation.

A system property is used to set the list of Ant-style patterns. Users need to add cb.backup.restore.keepFilesPattern to the system properties. For example, -Dcb.backup.restore.keepFilesPattern='.snapshots,**/.snapshots' has to be added to the system properties, to preserve `.snapshots filesystem control files in the $JENKINS_HOME directory during the restore process.

See Restoring from the CloudBees Backup Plugin for more information.

Known issues

Version 4.0 or higher of .NET Framework is required to launch controller or agents on Windows services

Starting from this release, .NET Framework 2.0 doesn’t work for launching CloudBees controller or agents as Windows services. Microsoft.NET Framework 4.0 or above is now required for using the default service management features.

This release also upgrades Windows Service Wrapper (WinSW) from 2.3.0 to 2.9.0 and replaces the bundled binary from .NET Framework 2.0 to 4.0. There are many improvements and fixes in these versions, big thanks to NextTurn and all other contributors. You can find the full WinSW changelog here, just a few highlights important to CloudBees users:

  • Prompt for permission elevation when administrative access is required. Now CloudBees users do not need to run the agent process as Administrator to install the agent as a service from GUI.

  • Enable TLS 1.1/1.2 in .NET Framework 4.0 packages on Windows 7 and Windows Server 2008 R2.

  • Enable strong cryptography when running .NET Framework 4.0 binaries on .NET 4.6.

  • Support security descriptor string in the Windows service definition.

  • Support 'If-Modified-Since' and proxy settings for automatic downloads.

  • Fix Runaway Process Killer extension so that it does not kill wrong processes with the same PID on startup.

  • Fix the default domain name in the serviceaccount parameter (jira:JENKINS-12660[])

  • Fix archiving of old logs in the roll-by-size-time mode.

Use-cases affected by .NET Framework 2.0 support removal

If you use .NET Framework 2.0 to run the CloudBees Windows services, the following use cases are likely to be affected:

  • Installing the CloudBees controller as a Windows service from Web UI. The official MSI Installer supports .NET Framework 2.0 for the moment, but it will be changed in future versions.

  • Installing agents as Windows services from GUI. This feature is provided by the Windows Agent Installer Module from the Jenkins core.

  • Installing agents over Windows Management Instrumentation (WMI) via the WMI Windows Agents plugin

  • Auto-updating of Windows service wrappers on agents installed from GUI.

Upgrade guidelines

If all of your CloudBees controller and agent instances already use .NET Framework 4.0 or above, there are no special upgrade steps required.

If you run the CloudBees controller as a Windows Service with .NET Framework 2.0, this instance will require an upgrade of .NET Framework to version 4.0 or above. .NET Framework 4.6.1 or above is recommended because this .NET version provides many platform features by default (e.g. TLS 1.2 encryption and strong cryptography), and Windows Service Wrapper does not have to apply custom workarounds.

If you want to continue running some of your agents with .NET Framework 2.0, the following extra upgrade steps are required:

  1. Disable auto-upgrade of Windows Service Wrapper on agents by setting the -Dorg.jenkinsci.modules.windows_slave_installer.disableAutoUpdate=true flag on the CloudBees controller side.

  2. Upgrade agents with .NET Framework 4.0+ by downloading the recent Windows Service Wrapper 2.x version from WinSW GitHub Releases and manually replacing the wrapper ".exe" files in the agent workspaces.

Upgrade notes

CloudBees High Availability plugin

CloudBees has upgraded the JGroups dependency for the CloudBees High Availability plugin, which means instances with JGroups customized through the GUI fail to start and existing jgroups.xml files may no longer be compatible.

Users with instances using the CloudBees High Availability plugin with JGroups customized through the GUI (under Manage Jenkins > Configure System > High Availability Configuration) must be updated to 2.249.2.4 or higher.

Users with instances that have a customized jgroups.xml file in $JENKINS_HOME must update it manually (or switch to using our defaults). See Upgrade guide for instances running High Availability previous to 2.249.2.3 for more information on customizing the configuration.

CloudBees Jenkins Distribution

The following are highlights of the October 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.

Security advisory

No security advisory with this release.

New features

None.

Feature enhancements

Beekeeper plugin exceptions

The following enhancements were made to the Beekeeper plugin exceptions feature:

  • User warned when specific plugins are saved as exceptions (FNDJEN-2409)

    When a plugin catalog containing Beekeeper plugin exceptions is selected on the master configuration page, a warning advising users of the implications associated with Beekeeper plugin exceptions is displayed.

  • Send event when Beekeeper plugin exceptions are enabled or disabled (FNDJEN-2421)

    If the CloudBees Assurance Program is enabled on an instance, CloudBees receives a weekly event to indicate if Beekeeper plugin exceptions were allowed or disallowed on that instance.

New option added to the restore configuration section of Restore/Backup jobs (CTR-2295)(CTR-2501)

CloudBees has added a new option to the restore configuration section of Restore/Backup jobs.

Users can now add a comma-separated list of Ant-style patterns to preserve content in the current JENKINS_HOME directory during the restore process, excluding it from the move operation.

A system property is used to set the list of Ant-style patterns. Users need to add cb.backup.restore.keepFilesPattern to the system properties. For example, -Dcb.backup.restore.keepFilesPattern='.snapshots,**/.snapshots' has to be added to the system properties, to preserve `.snapshots filesystem control files in the $JENKINS_HOME directory during the restore process.

See Restoring from the CloudBees Backup Plugin for more information.

Known issues

Version 4.0 or higher of .NET Framework is required to launch controller or agents on Windows services

Starting from this release, .NET Framework 2.0 doesn’t work for launching CloudBees controller or agents as Windows services. Microsoft.NET Framework 4.0 or above is now required for using the default service management features.

This release also upgrades Windows Service Wrapper (WinSW) from 2.3.0 to 2.9.0 and replaces the bundled binary from .NET Framework 2.0 to 4.0. There are many improvements and fixes in these versions, big thanks to NextTurn and all other contributors. You can find the full WinSW changelog here, just a few highlights important to CloudBees users:

  • Prompt for permission elevation when administrative access is required. Now CloudBees users do not need to run the agent process as Administrator to install the agent as a service from GUI.

  • Enable TLS 1.1/1.2 in .NET Framework 4.0 packages on Windows 7 and Windows Server 2008 R2.

  • Enable strong cryptography when running .NET Framework 4.0 binaries on .NET 4.6.

  • Support security descriptor string in the Windows service definition.

  • Support 'If-Modified-Since' and proxy settings for automatic downloads.

  • Fix Runaway Process Killer extension so that it does not kill wrong processes with the same PID on startup.

  • Fix the default domain name in the serviceaccount parameter (jira:JENKINS-12660[])

  • Fix archiving of old logs in the roll-by-size-time mode.

Use-cases affected by .NET Framework 2.0 support removal

If you use .NET Framework 2.0 to run the CloudBees Windows services, the following use cases are likely to be affected:

  • Installing the CloudBees controller as a Windows service from Web UI. The official MSI Installer supports .NET Framework 2.0 for the moment, but it will be changed in future versions.

  • Installing agents as Windows services from GUI. This feature is provided by the Windows Agent Installer Module from the Jenkins core.

  • Installing agents over Windows Management Instrumentation (WMI) via the WMI Windows Agents plugin

  • Auto-updating of Windows service wrappers on agents installed from GUI.

Upgrade guidelines

If all of your CloudBees controller and agent instances already use .NET Framework 4.0 or above, there are no special upgrade steps required.

If you run the CloudBees controller as a Windows Service with .NET Framework 2.0, this instance will require an upgrade of .NET Framework to version 4.0 or above. .NET Framework 4.6.1 or above is recommended because this .NET version provides many platform features by default (e.g. TLS 1.2 encryption and strong cryptography), and Windows Service Wrapper does not have to apply custom workarounds.

If you want to continue running some of your agents with .NET Framework 2.0, the following extra upgrade steps are required:

  1. Disable auto-upgrade of Windows Service Wrapper on agents by setting the -Dorg.jenkinsci.modules.windows_slave_installer.disableAutoUpdate=true flag on the CloudBees controller side.

  2. Upgrade agents with .NET Framework 4.0+ by downloading the recent Windows Service Wrapper 2.x version from WinSW GitHub Releases and manually replacing the wrapper ".exe" files in the agent workspaces.

CloudBees Jenkins Platform

The following are highlights of the October 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.

Security advisory

No security advisory with this release.

New features

None.

Feature enhancements

Add Pipeline Policies section to the SCM reporting commit status (STICKY-463)

If the CloudBees Pipeline Policies Plugin is installed, users will now see information that includes the applied policies and the violated rules.

Update Pipeline Policies report in Slack message (STICKY-740)

The CloudBees Pipeline Policies report within the CloudBees Slack Integration message now shows information about the applied policy and not only the violated rule.

Improve the observability and error logging of the configuration bundle installation (CTR-2302)

When there is an error during CasC bundle processing, a detailed summary is printed to logs. The summary includes whether the plugin catalog was or was not installed as well as the list of plugins not installed.

We added REST API endpoints and CLI commands for the following CasC actions (CTR-2247)
  • list available bundles in Operations Center

  • regenerate a Configuration as Code (CasC) for Masters bundle token for a specific bundle

  • assign a Master Path to a Configuration as Code (CasC) for Masters bundle

    See CasC API endpoints and CasC CLI commands for more information.

Improve UX of exporting Core CasC bundle(CTR-922)

Users with CloudBees CI masters that have the Configuration as Code (CasC) for Masters plugin installed can now view and export the applicable Configuration as Code (CasC) for Masters bundle, by navigating to Manage Jenkins > Export CloudBees Configuration as Code bundle.

Beekeeper plugin exceptions

The following enhancements were made to the Beekeeper plugin exceptions feature:

  • User warned when specific plugins are saved as exceptions (FNDJEN-2409)

    When a plugin catalog containing Beekeeper plugin exceptions is selected on the master configuration page, a warning advising users of the implications associated with Beekeeper plugin exceptions is displayed.

  • Send event when Beekeeper plugin exceptions are enabled or disabled (FNDJEN-2421)

    If the CloudBees Assurance Program is enabled on an instance, CloudBees receives a weekly event to indicate if Beekeeper plugin exceptions were allowed or disallowed on that instance.

New option added to the restore configuration section of Restore/Backup jobs (CTR-2295)(CTR-2501)

CloudBees has added a new option to the restore configuration section of Restore/Backup jobs.

Users can now add a comma-separated list of Ant-style patterns to preserve content in the current JENKINS_HOME directory during the restore process, excluding it from the move operation.

A system property is used to set the list of Ant-style patterns. Users need to add cb.backup.restore.keepFilesPattern to the system properties. For example, -Dcb.backup.restore.keepFilesPattern='.snapshots,**/.snapshots' has to be added to the system properties, to preserve `.snapshots filesystem control files in the $JENKINS_HOME directory during the restore process.

See Restoring from the CloudBees Backup Plugin for more information.

Known issues

Version 4.0 or higher of .NET Framework is required to launch controller or agents on Windows services

Starting from this release, .NET Framework 2.0 doesn’t work for launching CloudBees controller or agents as Windows services. Microsoft.NET Framework 4.0 or above is now required for using the default service management features.

This release also upgrades Windows Service Wrapper (WinSW) from 2.3.0 to 2.9.0 and replaces the bundled binary from .NET Framework 2.0 to 4.0. There are many improvements and fixes in these versions, big thanks to NextTurn and all other contributors. You can find the full WinSW changelog here, just a few highlights important to CloudBees users:

  • Prompt for permission elevation when administrative access is required. Now CloudBees users do not need to run the agent process as Administrator to install the agent as a service from GUI.

  • Enable TLS 1.1/1.2 in .NET Framework 4.0 packages on Windows 7 and Windows Server 2008 R2.

  • Enable strong cryptography when running .NET Framework 4.0 binaries on .NET 4.6.

  • Support security descriptor string in the Windows service definition.

  • Support 'If-Modified-Since' and proxy settings for automatic downloads.

  • Fix Runaway Process Killer extension so that it does not kill wrong processes with the same PID on startup.

  • Fix the default domain name in the serviceaccount parameter (jira:JENKINS-12660[])

  • Fix archiving of old logs in the roll-by-size-time mode.

Use-cases affected by .NET Framework 2.0 support removal

If you use .NET Framework 2.0 to run the CloudBees Windows services, the following use cases are likely to be affected:

  • Installing the CloudBees controller as a Windows service from Web UI. The official MSI Installer supports .NET Framework 2.0 for the moment, but it will be changed in future versions.

  • Installing agents as Windows services from GUI. This feature is provided by the Windows Agent Installer Module from the Jenkins core.

  • Installing agents over Windows Management Instrumentation (WMI) via the WMI Windows Agents plugin

  • Auto-updating of Windows service wrappers on agents installed from GUI.

Upgrade guidelines

If all of your CloudBees controller and agent instances already use .NET Framework 4.0 or above, there are no special upgrade steps required.

If you run the CloudBees controller as a Windows Service with .NET Framework 2.0, this instance will require an upgrade of .NET Framework to version 4.0 or above. .NET Framework 4.6.1 or above is recommended because this .NET version provides many platform features by default (e.g. TLS 1.2 encryption and strong cryptography), and Windows Service Wrapper does not have to apply custom workarounds.

If you want to continue running some of your agents with .NET Framework 2.0, the following extra upgrade steps are required:

  1. Disable auto-upgrade of Windows Service Wrapper on agents by setting the -Dorg.jenkinsci.modules.windows_slave_installer.disableAutoUpdate=true flag on the CloudBees controller side.

  2. Upgrade agents with .NET Framework 4.0+ by downloading the recent Windows Service Wrapper 2.x version from WinSW GitHub Releases and manually replacing the wrapper ".exe" files in the agent workspaces.

Upgrade notes

CloudBees High Availability plugin

CloudBees has upgraded the JGroups dependency for the CloudBees High Availability plugin, which means instances with JGroups customized through the GUI fail to start and existing jgroups.xml files may no longer be compatible.

Users with instances using the CloudBees High Availability plugin with JGroups customized through the GUI (under Manage Jenkins > Configure System > High Availability Configuration) must be updated to 2.249.2.4 or higher.

Users with instances that have a customized jgroups.xml file in $JENKINS_HOME must update it manually (or switch to using our defaults). See Upgrade guide for instances running High Availability previous to 2.249.2.3 for more information on customizing the configuration.

CloudBees CD

The following are highlights of the CloudBees CD October 2020 preview release. Refer to the full release notes for a complete list of changes, including resolved issues.

Security updates

None.

CloudBees CD plugin update highlights

Audit and compliance reports

Native audit reports are now available in CloudBees CD. These reports aggregate data generated and collected throughout CloudBees CI and CloudBees CD processes into easy to read reports that address auditing requirements of CloudBees CD customers.

Documentation:

External credential management support

Credential management capability has been extended to support external credential providers. External credentials are abstracted from the external management system and stored in CloudBees CD as references. Workflow to attach external credentials to plugins, procedures, and steps is identical to that for local credentials. At runtime, external credentials are retrieved on-demand from the external management system. [NMB-29479]

Supported external credential management systems include:

  • CyberArk: Dynamic Access Provider (DAP) and Central Credential Provider (CCP)

  • HashiCorp Vault: CUBBYHOLE, KV1 and KV2 secret engines

CloudBees CD UI support added to define external credential manager providers

Documentation:

CloudBees CD API changes: * Added new CredentialProvider API. * Enhanced Credential Management API with new credentialProviderName to reference provider for external credentials.

Enhanced discovery for CloudBees CI controllers

Completed integration where CloudBees CD can now connect directly to a CloudBees CI operations center to automatically discover and update the list of connected controllers on which a CI Job CloudBees CD pipeline task can run, amplifying the value across both products. This streamlines creation and management of controller configurations. [CEV-25661]

  • Enhanced CI configuration UI to support CloudBees CI operations center configurations.

  • Added support to discover CI Controllers from CloudBees CI operations center

API changes:

  • Added support to filter CI configurations by ciConfigurationType.

  • Enhanced the CI_JOB task type to support referencing a CI Job using a CI Configuration of type CB_OPS_CENTER CI configuration.

Updated Schedules UI page

The Schedules automation platform page is now available from the CloudBees CD UI via DevOps Essentials  Schedules on the main CloudBees CD menu. [NMB-25556]

Proxy support for CloudBees CD agents

Server-side environment variable definition support added for job steps running on the agent. These properties may be created under zone and/or resource entities in the special ec_environment_variables property sheet. If ec_environment_variables property sheet does not exist, manually create it under zone and/or resource objects to define environment variables. [NMB-29614]

  • Property to define environment variable for http proxy resource

      -> properties
        -> property sheet ec_environment_variables
          -> http_proxy = http://user:password@your-proxy-ip-address:port/
  • Property to define environment variable for https proxy resource

      -> properties
        -> property sheet ec_environment_variables
          -> http_proxy = https://user:password@your-proxy-ip-address:port/

Expanded --filters parameter support with ectool

The getPipelineRuntimes API now supports the --filters parameter when invoked with ectool. [CEV-25946]

CloudBees CD plugin updates

EC-Sendmail

Fixed parameter handling when the plugin is used in a component process step. [FLOWPLUGIN-8626]

EC-Helm

  • Changed configuration handling: If a file is provided for the configuration, the file is used, if the content of configuration file is provided, a temporary file is created to use with the plugin procedures. [FLOWPLUGIN-8643]

  • Fixed an issue with spaces in Helm chart path. [FLOWPLUGIN-8595]

EC-BigIP

Added token cleanup (logout) at each plugin step. [FLOWPLUGIN-8614]

EC-Docker

The Artifact2Image procedure now supports Artifactory extract boolean and classifier.[FLOWPLUGIN-7818, FLOWPLUGIN-7817]

Plugin support changes

The following plugins are being moved to community support going forward as of CloudBees CD preview release 2020.10.0. Log change requests or issues on their respective GitHub projects. Customers are encouraged to explore changing these plugins directly as required.

ECSCM-Perforce

ECSCM-Repo

ECSCM-SVN

ECSCM-TFS

EC-Tutorials

EC-Jetty

EC-MSBuild

EC-Powershell

EC-Puppet

CloudBees Build Acceleration

The following are highlights of the CloudBees Build Acceleration October 2020 preview release. Refer to the full release notes for a complete list of changes.

Redesigned and expanded Build Details

The Build Details page in the cluster manager has been redesigned and expanded to include performance analysis and visualizations derived from CloudBees Build Acceleration Insight. This enhancement enables users and administrators to easily access the most critical performance data for builds from any system that can access the cluster manager web interface, even if the annotation file for the build is not accessible.

The Build Details page now includes new sub-tabs for Timeline, Composition, Jobcache, Performance, and Diagnostics.

Android 11 support

This release extends the Android build integration to support builds based on AOSP 11.0.0_r3.

Bitbake support

This release extends Bitbake integration with support for packages that build using ninja instead of make, resulting in improved performance for Bitbake/Yocto users (EC-13789). In addition, the bb2anno utility has been enhanced to aggregate the data in <metrics> sections of the individual annotation files that are incorporated into the combined annotation file, to improve "whole build" performance analysis (EC-13956).

Security configuration

This release adds support for configuring agent security settings during installation and after installation with ecconfig. Security settings configured using these methods will be preserved during future upgrades. (EC-13407).

Automatic output directory creation

This release introduces a new command-line option for emake, --emake-create-output-dirs. When enabled, this will cause emake to automatically and efficiently create output directories for targets when running in GMake emulation modes. In addition, the details of the implementation are such that this will avoid provoking conflicts even in builds that have no history file or have an incomplete history file. (EC-13680).

Build signatures and totality

This release adds "build signatures", a hash computed from the serial ordered list of output targets in the build. This value can be used to identify builds that are substantively "the same" to facilitate comparisons and identification of trends across sets of like builds. The hash uses emake-root-relative target names, so the signature will be the same even if the absolute location of the build has changed

CloudBees Build Acceleration Insight

This release includes an updated preview release of CloudBees Build Acceleration Insight with the following enhancements:

  • A new JobCache Summary report which provides an overview of jobcache use in the build (EI-845).

  • The Diagnostics report includes module and target name information in the command-line output (EI-853), and limits the number of results printed in both the GUI and command-line versions (EI-852).

In addition this release includes a variant of CloudBees Build Acceleration Insight specifically for command-line use on Linux, called einsight-cmd. This variant has no dependencies on GUI libraries, making it ideal for use in "headless" automation contexts.

CloudBees Software Delivery Management

No updates.