September 2020 product highlights
CloudBees CI on modern cloud platforms
The following are highlights of the September 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.
New features
- Beekeeper plugin exceptions (FNDJEN-2567)
-
Beekeeper plugin exceptions provide a way to fix urgent bugs or security issues related to plugins by upgrading to a version of a plugin that is not yet available in the CloudBees Assurance Program.
See Beekeeper plugin exceptions for more information.
Feature enhancements
- Add category for ElasticSearch Reporter Plugin (CPLT2-6669)
-
The ElasticSearch Reporter configuration button was moved from the Uncategorized section of the /manage page to the System Configuration section.
- Allow CloudBees SCM Reporting to be opt-in (STICKY-667)
-
The CloudBees CI SCM Reporting feature was enabled by default whenever the plugin was installed, which for installations with numerous projects could be an unwelcome surprise.
For discoverability, the feature remains on by default, but there is now a checkbox in the master system configuration to disable it by default without disabling the plugin. Users can disable it by default via GUI or configuration as code. Notifications may still be turned on or off (or further customized) for a particular project in that project’s configuration screen.
See Configuring CloudBees SCM Reporting notifications for more information.
- CloudBees SCM Reporting GitHub Re-run link enabled (STICKY-171)
-
Failing tests displayed on the GitHub Checks tab included a Re-run link but the link was disabled.
Now, selecting the Re-run link triggers a new build in CloudBees CI.
See Viewing GitHub Checks tab notifications for more information.
- Add Rebuild button to CloudBees Slack Integration message (STICKY-493)
-
When a PR cannot be successfully built in CloudBees CI, the CloudBees Slack Integration message now includes a Rebuild button that will trigger a new build.
When a new build is started, the previous messages that contain a Rebuild button are updated, so the button is removed to prevent the user from selecting an invalid/out-of-date message.
See Actionable build notifications in Slack with CloudBees Jenkins Platform Slack Integration for more information.
- Enable link to build in the first line of the CloudBees Slack Integration message (STICKY-717)
-
Before, the initial line of the CloudBees Slack Integration message included a reference to the build number, but did not link to the build.
Now the build reference on the first line of the CloudBees Slack Integration message links to the build.
See Actionable build notifications in Slack with CloudBees Jenkins Platform Slack Integration for more information.
- Verify if the CloudBees Slack Integration user exists before adding a new user (STICKY-670)
-
When adding a CloudBees Slack Integration new user, if a user is already configured or the user does not exist, the administrator will now receive a warning message. Also, if the user is already configured, the message will prevent the admin from adding the new user.
The same validation is checked if the admin is updating an existing user.
- Improved Configuration as Code (CasC) for Masters export output (CTR-2207)
-
The readability of the output produced for a Configuration as Code (CasC) for Masters export has been improved in the following ways:
-
There are now yaml
---document separators between the different documents. -
The plugin list will now be alphabetized.
-
- The email-ext plugin and Configuration as Code (FNDJEN-2110)
-
This plugin is now compatible with Configuration as Code.
- Jenkins user interface updates (FNDJEN-2723, FNDJEN-2237, FNDJEN-2232, FNDJEN-2193, FNDJEN-2025, FNDJEN-2691)
-
As part of CloudBees' ongoing effort to update the Jenkins user interface, the following enhancements were made:
-
Colors were normalized in different widgets to be consistent with the new color palette.
-
Tables were restyled with more inner spacing to improve readability. The tables also now use colors that are consistent with the rest of the UI.
-
Hyperlink styles were updated.
-
Side panel widgets were restyled to have a more modern look.
-
Sidebar task list appearance and accessibility were improved.
-
- Warnings NG plugin included in CAP (STICKY-633)
-
One of the most popular OSS plugins, Warnings Next Generation, is now part of the CloudBees Assurance Program (CAP).
Using the Warnings NG plugin greatly enriches the information surfaced through the CloudBees SCM, Slack, and Microsoft Teams Integration plugins.
While the Warnings NG plugin could be used with these plugins before, for customers who strictly use CAP plugins, it was not previously an option.
- Allow/disallow Beekeeper Plugin Exceptions (CTR-2197)
-
A connected master can be configured to allow/disallow Beekeeper Plugin Exceptions from the master configuration page.
- Upgraded CloudBees Fast Archiving Plugin dependencies (CTR-2281)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 andcommons-netis 3.6, which are compatible with Jenkins 2.250. - Upgraded CloudBees Request Filter Plugin dependencies (CTR-2284)
-
The parent pom dependency
nectar-licenseis now 8.28 which is compatible with Jenkins 2.250. - Upgraded CloudBees RBAC Auto Configurer plugin dependencies (CTR-2279)
-
The parent pom dependency and
org.jenkins-ci.plugins:structsare now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Groovy View Plugin dependencies (CTR-2283)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Skip Next Build Plugin dependencies (CTR-2278)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Restart Aborted Builds Plugin dependencies (CTR-2280)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now version 1.20 andorg.jenkins-ci:symbol-annotationis 1.20. Both are compatible with Jenkins version 2.250. - Upgraded Notification API plugin dependencies (CTR-2285)
-
The Notification API plugin now uses Jenkins Configuration as Code (JCasC) version 1.40 which is compatible with Jenkins version 2.250 and above.
- Upgraded CloudBees Backup Plugin dependencies (CTR-2282)
-
The plugin dependency
org.jenkins-ci.plugins:structsis now compatible with Jenkins 2.250. - [JENKINS-48837] Add
BranchPropertysupport toOrganizationFolder(NGPIPELINE-1314) -
Multibranch Pipeline jobs have an option to configure Branch Property Strategies. Org folders did not support this Branch Property Strategy configuration. This prevented the child Multibranch Pipeline jobs from having Branch Property Strategies configured.
With this fix, we added the ability for Org folders to configure Branch Property Strategies for their Multibranch Pipeline children.
CloudBees CI on traditional platforms
The following are highlights of the September 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.
New features
- Beekeeper plugin exceptions (FNDJEN-2567)
-
Beekeeper plugin exceptions provide a way to fix urgent bugs or security issues related to plugins by upgrading to a version of a plugin that is not yet available in the CloudBees Assurance Program.
See Beekeeper plugin exceptions for more information.
Feature enhancements
- Add category for ElasticSearch Reporter Plugin (CPLT2-6669)
-
The ElasticSearch Reporter configuration button was moved from the Uncategorized section of the /manage page to the System Configuration section.
- Client Master security: Get rid of visible "slave" words (CTR-2070)
-
Replace "slaves" term with "agents".
- Allow CloudBees SCM Reporting to be opt-in (STICKY-667)
-
The CloudBees CI SCM Reporting feature was enabled by default whenever the plugin was installed, which for installations with numerous projects could be an unwelcome surprise.
For discoverability, the feature remains on by default, but there is now a checkbox in the master system configuration to disable it by default without disabling the plugin. Users can disable it by default via GUI or configuration as code. Notifications may still be turned on or off (or further customized) for a particular project in that project’s configuration screen.
See Configuring CloudBees SCM Reporting notifications for more information.
- CloudBees SCM Reporting GitHub Re-run link enabled (STICKY-171)
-
Failing tests displayed on the GitHub Checks tab included a Re-run link but the link was disabled.
Now, selecting the Re-run link triggers a new build in CloudBees CI.
See Viewing GitHub Checks tab notifications for more information.
- Add Rebuild button to CloudBees Slack Integration message (STICKY-493)
-
When a PR cannot be successfully built in CloudBees CI, the CloudBees Slack Integration message now includes a Rebuild button that will trigger a new build.
When a new build is started, the previous messages that contain a Rebuild button are updated, so the button is removed to prevent the user from selecting an invalid/out-of-date message.
See Actionable build notifications in Slack with CloudBees Jenkins Platform Slack Integration for more information.
- Enable link to build in the first line of the CloudBees Slack Integration message (STICKY-717)
-
Before, the initial line of the CloudBees Slack Integration message included a reference to the build number, but did not link to the build.
Now the build reference on the first line of the CloudBees Slack Integration message links to the build.
See Actionable build notifications in Slack with CloudBees Jenkins Platform Slack Integration for more information.
- Verify if the CloudBees Slack Integration user exists before adding a new user (STICKY-670)
-
When adding a CloudBees Slack Integration new user, if a user is already configured or the user does not exist, the administrator will now receive a warning message. Also, if the user is already configured, the message will prevent the admin from adding the new user.
The same validation is checked if the admin is updating an existing user.
- Improved Configuration as Code (CasC) for Masters export output (CTR-2207)
-
The readability of the output produced for a Configuration as Code (CasC) for Masters export has been improved in the following ways:
-
There are now yaml
---document separators between the different documents. -
The plugin list will now be alphabetized.
-
- The email-ext plugin and Configuration as Code (FNDJEN-2110)
-
This plugin is now compatible with Configuration as Code.
- Jenkins user interface updates (FNDJEN-2723, FNDJEN-2237, FNDJEN-2232, FNDJEN-2193, FNDJEN-2025, FNDJEN-2691)
-
As part of CloudBees' ongoing effort to update the Jenkins user interface, the following enhancements were made:
-
Colors were normalized in different widgets to be consistent with the new color palette.
-
Tables were restyled with more inner spacing to improve readability. The tables also now use colors that are consistent with the rest of the UI.
-
Hyperlink styles were updated.
-
Side panel widgets were restyled to have a more modern look.
-
Sidebar task list appearance and accessibility were improved.
-
- Warnings NG plugin included in CAP (STICKY-633)
-
One of the most popular OSS plugins, Warnings Next Generation, is now part of the CloudBees Assurance Program (CAP).
Using the Warnings NG plugin greatly enriches the information surfaced through the CloudBees SCM, Slack, and Microsoft Teams Integration plugins.
While the Warnings NG plugin could be used with these plugins before, for customers who strictly use CAP plugins, it was not previously an option.
- Allow/disallow Beekeeper Plugin Exceptions (CTR-2197)
-
A connected master can be configured to allow/disallow Beekeeper Plugin Exceptions from the master configuration page.
- Upgraded CloudBees Fast Archiving Plugin dependencies (CTR-2281)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 andcommons-netis 3.6, which are compatible with Jenkins 2.250. - Upgraded CloudBees Request Filter Plugin dependencies (CTR-2284)
-
The parent pom dependency
nectar-licenseis now 8.28 which is compatible with Jenkins 2.250. - Upgraded CloudBees RBAC Auto Configurer plugin dependencies (CTR-2279)
-
The parent pom dependency and
org.jenkins-ci.plugins:structsare now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Groovy View Plugin dependencies (CTR-2283)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Skip Next Build Plugin dependencies (CTR-2278)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Restart Aborted Builds Plugin dependencies (CTR-2280)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now version 1.20 andorg.jenkins-ci:symbol-annotationis 1.20. Both are compatible with Jenkins version 2.250. - Upgraded Notification API plugin dependencies (CTR-2285)
-
The Notification API plugin now uses Jenkins Configuration as Code (JCasC) version 1.40 which is compatible with Jenkins version 2.250 and above.
- Upgraded CloudBees Backup Plugin dependencies (CTR-2282)
-
The plugin dependency
org.jenkins-ci.plugins:structsis now compatible with Jenkins 2.250. - [JENKINS-48837] Add
BranchPropertysupport toOrganizationFolder(NGPIPELINE-1314) -
Multibranch Pipeline jobs have an option to configure Branch Property Strategies. Org folders did not support this Branch Property Strategy configuration. This prevented the child Multibranch Pipeline jobs from having Branch Property Strategies configured.
With this fix, we added the ability for Org folders to configure Branch Property Strategies for their Multibranch Pipeline children.
CloudBees Jenkins Distribution
The following are highlights of the September 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.
New features
None.
- Beekeeper plugin exceptions (FNDJEN-2567)
-
Beekeeper plugin exceptions provide a way to fix urgent bugs or security issues related to plugins by upgrading to a version of a plugin that is not yet available in the CloudBees Assurance Program.
See Beekeeper plugin exceptions for more information.
Feature enhancements
- The email-ext plugin and Configuration as Code (FNDJEN-2110)
-
This plugin is now compatible with Configuration as Code.
- Jenkins user interface updates (FNDJEN-2723, FNDJEN-2237, FNDJEN-2232, FNDJEN-2193, FNDJEN-2025, FNDJEN-2691)
-
As part of CloudBees' ongoing effort to update the Jenkins user interface, the following enhancements were made:
-
Colors were normalized in different widgets to be consistent with the new color palette.
-
Tables were restyled with more inner spacing to improve readability. The tables also now use colors that are consistent with the rest of the UI.
-
Hyperlink styles were updated.
-
Side panel widgets were restyled to have a more modern look.
-
Sidebar task list appearance and accessibility were improved.
-
- Warnings NG plugin included in CAP (STICKY-633)
-
One of the most popular OSS plugins, Warnings Next Generation, is now part of the CloudBees Assurance Program (CAP).
Using the Warnings NG plugin greatly enriches the information surfaced through the CloudBees SCM, Slack, and Microsoft Teams Integration plugins.
While the Warnings NG plugin could be used with these plugins before, for customers who strictly use CAP plugins, it was not previously an option.
- Allow/disallow Beekeeper Plugin Exceptions (CTR-2197)
-
A connected master can be configured to allow/disallow Beekeeper Plugin Exceptions from the master configuration page.
- Upgraded CloudBees Fast Archiving Plugin dependencies (CTR-2281)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 andcommons-netis 3.6, which are compatible with Jenkins 2.250. - Upgraded CloudBees Request Filter Plugin dependencies (CTR-2284)
-
The parent pom dependency
nectar-licenseis now 8.28 which is compatible with Jenkins 2.250. - Upgraded CloudBees RBAC Auto Configurer plugin dependencies (CTR-2279)
-
The parent pom dependency and
org.jenkins-ci.plugins:structsare now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Groovy View Plugin dependencies (CTR-2283)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Skip Next Build Plugin dependencies (CTR-2278)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Restart Aborted Builds Plugin dependencies (CTR-2280)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now version 1.20 andorg.jenkins-ci:symbol-annotationis 1.20. Both are compatible with Jenkins version 2.250. - Upgraded Notification API plugin dependencies (CTR-2285)
-
The Notification API plugin now uses Jenkins Configuration as Code (JCasC) version 1.40 which is compatible with Jenkins version 2.250 and above.
- Upgraded CloudBees Backup Plugin dependencies (CTR-2282)
-
The plugin dependency
org.jenkins-ci.plugins:structsis now compatible with Jenkins 2.250. - [JENKINS-48837] Add
BranchPropertysupport toOrganizationFolder(NGPIPELINE-1314) -
Multibranch Pipeline jobs have an option to configure Branch Property Strategies. Org folders did not support this Branch Property Strategy configuration. This prevented the child Multibranch Pipeline jobs from having Branch Property Strategies configured.
With this fix, we added the ability for Org folders to configure Branch Property Strategies for their Multibranch Pipeline children.
CloudBees Jenkins Platform
The following are highlights of the September 2020 release. Refer to the full release notes for a complete list of changes, including resolved issues.
New features
- Beekeeper plugin exceptions (FNDJEN-2567)
-
Beekeeper plugin exceptions provide a way to fix urgent bugs or security issues related to plugins by upgrading to a version of a plugin that is not yet available in the CloudBees Assurance Program.
See Beekeeper plugin exceptions for more information.
Feature enhancements
- Allow CloudBees SCM Reporting to be opt-in (STICKY-667)
-
The CloudBees Jenkins Platform SCM Reporting feature was enabled by default whenever the plugin was installed, which for installations with numerous projects could be an unwelcome surprise.
For discoverability, the feature remains on by default, but there is now a checkbox in the master system configuration to disable it by default without disabling the plugin. Users can disable it by default via GUI or configuration as code. Notifications may still be turned on or off (or further customized) for a particular project in that project’s configuration screen.
See Configuring CloudBees SCM Reporting notifications for more information.
- CloudBees SCM Reporting GitHub Re-run link enabled (STICKY-171)
-
Failing tests displayed on the GitHub Checks tab included a Re-run link but the link was disabled.
Now, selecting the Re-run link triggers a new build in CloudBees Jenkins Platform.
See Viewing GitHub Checks tab notifications for more information.
- Add Rebuild button to CloudBees Slack Integration message (STICKY-493)
-
When a PR cannot be successfully built in CloudBees Jenkins Platform, the CloudBees Slack Integration message now includes a Rebuild button that will trigger a new build.
When a new build is started, the previous messages that contain a Rebuild button are updated, so the button is removed to prevent the user from selecting an invalid/out-of-date message.
See Actionable build notifications in Slack with CloudBees Jenkins Platform Slack Integration for more information.
- Enable link to build in the first line of the CloudBees Slack Integration message (STICKY-717)
-
Before, the initial line of the CloudBees Slack Integration message included a reference to the build number, but did not link to the build.
Now the build reference on the first line of the CloudBees Slack Integration message links to the build.
See Actionable build notifications in Slack with CloudBees Jenkins Platform Slack Integration for more information.
- Verify if the CloudBees Slack Integration user exists before adding a new user (STICKY-670)
-
When adding a CloudBees Slack Integration new user, if a user is already configured or the user does not exist, the administrator will now receive a warning message. Also, if the user is already configured, the message will prevent the admin from adding the new user.
The same validation is checked if the admin is updating an existing user.
- Improved Configuration as Code (CasC) for Masters export output (CTR-2207)
-
The readability of the output produced for a Configuration as Code (CasC) for Masters export has been improved in the following ways:
-
There are now yaml
---document separators between the different documents. -
The plugin list will now be alphabetized.
-
- The email-ext plugin and Configuration as Code (FNDJEN-2110)
-
This plugin is now compatible with Configuration as Code.
- Jenkins user interface updates (FNDJEN-2723, FNDJEN-2237, FNDJEN-2232, FNDJEN-2193, FNDJEN-2025, FNDJEN-2691)
-
As part of CloudBees' ongoing effort to update the Jenkins user interface, the following enhancements were made:
-
Colors were normalized in different widgets to be consistent with the new color palette.
-
Tables were restyled with more inner spacing to improve readability. The tables also now use colors that are consistent with the rest of the UI.
-
Hyperlink styles were updated.
-
Side panel widgets were restyled to have a more modern look.
-
Sidebar task list appearance and accessibility were improved.
-
- Warnings NG plugin included in CAP (STICKY-633)
-
One of the most popular OSS plugins, Warnings Next Generation, is now part of the CloudBees Assurance Program (CAP).
Using the Warnings NG plugin greatly enriches the information surfaced through the CloudBees SCM, Slack, and Microsoft Teams Integration plugins.
While the Warnings NG plugin could be used with these plugins before, for customers who strictly use CAP plugins, it was not previously an option.
- Allow/disallow Beekeeper Plugin Exceptions (CTR-2197)
-
A connected master can be configured to allow/disallow Beekeeper Plugin Exceptions from the master configuration page.
- Upgraded CloudBees Fast Archiving Plugin dependencies (CTR-2281)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 andcommons-netis 3.6, which are compatible with Jenkins 2.250. - Upgraded CloudBees Request Filter Plugin dependencies (CTR-2284)
-
The parent pom dependency
nectar-licenseis now 8.28 which is compatible with Jenkins 2.250. - Upgraded CloudBees RBAC Auto Configurer plugin dependencies (CTR-2279)
-
The parent pom dependency and
org.jenkins-ci.plugins:structsare now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Groovy View Plugin dependencies (CTR-2283)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Skip Next Build Plugin dependencies (CTR-2278)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis 1.20 which is compatible with Jenkins 2.250. - Upgraded CloudBees Restart Aborted Builds Plugin dependencies (CTR-2280)
-
The parent pom dependency
org.jenkins-ci.plugins:structsis now version 1.20 andorg.jenkins-ci:symbol-annotationis 1.20. Both are compatible with Jenkins version 2.250. - Upgraded Notification API plugin dependencies (CTR-2285)
-
The Notification API plugin now uses Jenkins Configuration as Code (JCasC) version 1.40 which is compatible with Jenkins version 2.250 and above.
- Upgraded CloudBees Backup Plugin dependencies (CTR-2282)
-
The plugin dependency
org.jenkins-ci.plugins:structsis now compatible with Jenkins 2.250. - [JENKINS-48837] Add
BranchPropertysupport toOrganizationFolder(NGPIPELINE-1314) -
Multibranch Pipeline jobs have an option to configure Branch Property Strategies. Org folders did not support this Branch Property Strategy configuration. This prevented the child Multibranch Pipeline jobs from having Branch Property Strategies configured.
With this fix, we added the ability for Org folders to configure Branch Property Strategies for their Multibranch Pipeline children.
CloudBees CD
The following are highlights of the CloudBees CD September 2020 preview release. Refer to the full release notes for a complete list of changes, including resolved issues.
Security updates
This release includes the following security updates. [NMB-29578]
-
The Apache web server used in CloudBees CD is upgraded from version 2.4.43 to 2.4.46. For details, see https://www.apache.org/dist/httpd/CHANGES_2.4.
-
PHP is upgraded from version 7.4.6 to 7.4.10. For details, see https://www.php.net/downloads.php.
Automatically discover native CI controllers
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.
-
Add support to discover CI Controllers from CloudBees CI operations center.
Documentation: Configuring CI controllers
Service catalog updates
These service catalog items have been deprecated: [CEV-25460]
-
Azure Container Service Discovery
-
Amazon ECS Dynamic Cluster
-
GCE Dynamic Cluster
Updated Procedures UI page
The Procedures automation platform page is now available from the CloudBees CD UI. Select Procedures from DevOps Essentials column on the main menu. [NMB-29515]
Documentation: CloudBees CD procedure details
Plugin developer guide availability
The Plugin Developer Guide is now available on the main product doc site. [CEV-25554]
Plugin doc migration to docs.cloudbees.com
Completed the first phase of plugin doc migration from the legacy Electric Cloud site to docs.cloudbees.com.
CloudBees CD plugin update highlights
EC-Artifactory v1.4.7
-
Fixed broken compressed files (.zip, 7z) on Windows. [FLOWPLUGIN-8442]
-
Maven artifacts now use
maven-metadata.xmlto get the latest version to avoid license restrictions. [FLOWPLUGIN-8130]
EC-Jenkins v1.18.1
Two revisions of EC-Jenkins plugin have been recently released.
1.18.0
-
New checkbox "Depend On Jenkins Build Result?" has been added to "Run And Wait" procedure. [FLOWPLUGIN-8557]
-
Auth Type parameter has been added to the plugin configuration. The plugin now supports Basic and Bearer Token auth.
-
Debug Levelparameter has been added to the plugin configuration. -
Collect Reporting Data procedure has been improved to have better support for Multibranch Pipeline.
-
Data source setup for Jenkins has been improved to have better support for Multibranch Pipeline.
EC-JIRA v 1.7.1
-
Added support for
fixVersionand add/remove tickets fromfixVersion. [FLOWPLUGIN-8391]
EC-SonarQube v 1.3.3
-
Fixed issues with plugin reporting
/myTask/taskName does not exist. [FLOWPLUGIN-8468]
ECSCM v2.3.4
-
Fixed an issue when disabled schedules were re-enabled after plugin upgrade. [FLOWPLUGIN-3414]
Jenkins plugin for CloudBees CD v1.18
-
Updated the
Publish Artifactpost-build action withRelative Workspaceparameter. -
Updated Run And Wait
checkIntervalby min value. -
Updated
Depend on CD job/pipeline outcomefunctionality by association of CloudBees CD job/pipeline outcomeWarningwith CloudBees CI build resultUnstable. -
Updated build summary links for
Run Pipeline,Publish Artifact,Trigger Release. -
Fixed snippet generator UI for pipeline steps with extra parameters (
Run Procedure,Trigger Release,Run Pipeline,Deploy Application). -
Event-based build watchers now send build information after the build is finished.
-
CloudBees CD multi-branch pipelines support has been improved.
-
Bug fixes and improvements.
CloudBees Build Acceleration
The following are highlights of the CloudBees Build Acceleration September 2020 preview release. Refer to the full release notes for a complete list of changes.
Performance Improvements
-
This release of CloudBees Build Acceleration includes several enhancements to improve Android incremental build performance, which can be enabled by regenerating the build history file with
--emake-history=createoption on a full build; later builds can be built without that option or when the value is set tomerge. The changes made include: -
The ninja parser no longer creates jobs for prerequisites that are mentioned only in
.ninja_deps. This avoids the cost of job processing for source files. (EC-13689) -
emake no longer stat’s order-only prerequisites during up-to-date checks. (EC-13923)
-
The Android integration pragmafiles (enabled when you use the
--emake-android-versionoption) have been retuned for Android 10 and Android 11 to avoid spurious rebuilds of up-to-date outputs during incremental builds and to reduce startup time. (EC-13916, EC-13915)
There is also an improvement in symbolic links handling, where timestamps on symlinks created during a build are in the correct relative order when compared to timestamps on regular files created during the build, improving efficiency of incremental builds. (EC-13444)
CloudBees Build Acceleration Insight
This release includes an updated preview release of CloudBees Build Acceleration Insight with the following enhancements:
-
A new "Diagnostics" report identifies error and warning messages in the build output log and has both graphical and command-line interfaces. (EI-843)
-
The "Job Time by Type" report can produce JSON formatted output when invoked from the command-line by adding a "json" parameter to the invocation. For example:
einsight --report="JobTimeByType json" emake.xml. (EI-848) -
The "Longest Serial Chain" report can produce JSON formatted output when invoked from the command-line by adding a "json" parameter to the invocation. For example, to generate the longest serial chain overall in json format, use
einsight --report="LongestSerialChain overall json" emake.xml. (EI-844)
Behavior changes
bemake configuration files have been renamed bemake_package_accelerated and bemake_package_exceptions as part of CloudBees' commitment to inclusivity. For backwards compatibility the legacy names bemake_package_whitelist and bemake_package_blacklist will be used if files matching the new names cannot be found, but the names are deprecated and users are encouraged to rename these files in their setup when possible. (EC-13892)
CloudBees SDM
CloudBees announced general availability in Q4 of software delivery management modules: Engineering Efficiency and Feature Management. Read the full press release.