Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction

Helm plugin release notes

2 minute readExtensibilityDeveloper productivity

1.9.3

  • Updated the Revision number parameter to be optional in the Rollback Release procedure.

1.9.2

  • To help track their progress, deployements steps of rollouts were updated with mesages that show the completed number of steps.

  • Fixed an issue where the Environment Inventory returned non-existed artifact versions.

1.9.1

  • Fixed an issue with the canary deployment strategy where a microservice deployment was incorrectly promoted despite being aborted at the second pause stage.

  • Fixed an issue with the canary deployment strategy where a microservice deployment was incorrectly reporting the version to Inventory at first pause proceeding.

1.9.0

  • Upgraded dependencies.

  • Migrated to Java 17 and Groovy 3.

    The EC-Helm plugin v1.9.0 and later now requires CloudBees CD/RO agents with version 10.11 and later.

1.8.0

  • Seed inventory with warning status for aborted deployments.

  • When using CloudBees CD/RO microservice deployments that include Argo Rollouts inline analysis, the plugin now creates a manual approval step in the deployment pipeline step if an inconclusive state is returned.

  • Improved error handling for the Delete Release procedure.

  • Upgraded from Perl 5.8 to Perl 5.32. The plugin is not backward compatible with CloudBees CD/RO versions prior to 10.3. Starting from this release, a new agent is required to run EC-Helm plugin procedures.

1.7.1

  • Fixed inventory cleaning when the application and environment are in different projects.

  • Upgraded SnakeYAML to v2.0.

1.7.0

  • Internal improvements for CloudBees CD/RO microservices deployment.

1.6.0

  • Added handling when Use existing is selected for the Config file parameter in the plugin configuration.

  • Added the Kubeconfig Context parameter to the plugin configuration.

  • Deprecated the Kubeconfig context parameter in the Cluster Reference form in microservices.

  • Fixed a security issue.

  • Fixed the hard-coded actionOnError parameter.

1.5.1

  • Fixed application deployment on agents in version 10.5.

  • Fixed removing duplicate parameters in the microservice definition form.

1.5.0

  • Enabled support of new configurations.

1.4.1

  • Added the Compatibility property for the source provider.

1.3.0

  • Added optional auto-rollback support for Microservices.

  • Cosmetic UI changes were made to the Create Configuration procedure.

  • Improvements were made to retain the environment inventory in its actual state.

  • Added a Chart Version parameter to the microservice definition form.

  • Added the OpenShift: Deploying Jenkins using Helm v3 use case to the documentation.

1.2.0

  • Helm version v2 has been deprecated.

  • Added Microservices support.

  • Added the Values parameter to hold YAML content that is passed to the CLI as the values file for the following procedures:

  • Install Chart

  • Upgrade Release

  • Run Custom Command

1.1.4

  • Fixed parsing of RC versions of Helm.

1.1.3

  • Added the option to use custom config files.

1.1.2

  • The documentation has been migrated to the main documentation site.

1.1.1

  • Added an option for handling spaces in the path.

1.1.0

  • Added the option to create a kubeconfig.

1.0.0

  • The initial version of the plugin. The following procedures are supported:

  • Install Chart

  • Upgrade Release

  • Delete Release

  • Rollback Release

  • Run Custom Command

Known issues

For microservice deployments, you should use Helm version 3.4.0 or newer. Otherwise, the Helm plugin fails to retrieve the release details.

Third-party dependencies

Table 1. Third-party dependencies
Module License

org.yaml:snakeyaml:2.3

Apache License, Version 2.0
Helm plugin use cases