2.5.6
-
Updated third-party dependencies.
-
Fixed an issue where the
+
literal was not properly encoded when performing REST API calls using the runRest procedure.
2.5.3
-
Updated third-party dependencies.
-
Added default values to parameters not supported by legacy plugin configurations to prevent
null
value exceptions.
2.5.2
-
Added capability to the plugin setup procedure to process dependencies for CloudBees CD/RO IPv6 instances.
2.5.1
-
Updated the documentation and UI description for the Post-processing script shell parameter.
-
Improved the documentation and UI descriptions for custom header/prefix authentication types.
-
Updated third-party dependencies.
-
Fixed a problem where output parameters were incorrectly configured even though the REST call failed.
-
Fixed issue with symbolic links when extracting dependencies.
2.5.0
-
Updated third-party dependencies.
-
Migrated to Java 17 and Groovy 3.
Because of the Java versions supported by CloudBees CD/RO, you can only use EC-Rest v2.5.0 with CloudBees CD/RO agents v10.11 and later. -
Added support for using custom ports.
2.4.0
-
Upgraded dependencies.
-
Added support for HTTP/1.1 to negotiation protocols.
-
Migrated to PDK.
-
Added the Initial path URL and Default request timeout parameters to the plugin configuration.
2.2.0
-
Added the Download to a file option.
-
Added the Request timeout option.
-
Implemented token bearer authentication.
-
Added the Ignore SSL issues flag.
-
Implemented authentication with a custom header and/or prefix.
2.0.1
-
Fixed an issue with the post-processing script output returning
groovy.lang.MissingPropertyException
:No such property: sp for class: Rest.
-
Documented incompatibilities between v1 and v2.
2.0.0
-
Major plugin refactoring:
-
A new ec-groovy plugin framework was implemented to improve future plugin enhancements.
-
Added external credentials support.
-
1.1.0
-
Fixed parsing for headers with a whitespace.
-
Added support for HTTP proxies. Customers who use HTTP proxies can specify proxy information (host, port and credentials at the configuration level) and all procedures will use the proxy as second credentials for authentication.
-
RunRest procedure enhancements:
-
Additional Post Script parameters.
-
Output parameters.
-
Possibility to ignore authentication for a specific request.
-
Possibility to set the cookie value.
-
1.0.7
-
Added support for Commander credentials for basic authentication.
-
Masked credentials in step log file.
1.0.0
-
Added the runRest procedure.
-
Implemented the XML parameter panel.
-
Created the help page.
-
Created detailed examples.
-
Added
Postp
implementation.
Known issues
-
Incompatibilities between v1 and v2
After migration from v1 to v2, legacy v1 configurations are incompatible and must be recreated manually. Additionally, the runRest procedure uses the parameter
config
instead ofconnection_config
. Calls that use theconnection_config
parameter must be updated manually. -
Multiple instances of runRest after upgrading to v2
The
ec_setup.pl
script used in v1 always adds its step picker independently of the context and never removes it. Since the v1 step picker is not removed, the step picker will have two runRest instances after upgrading.To prevent the duplicate step pickers, after upgrade:
-
Uninstall the legacy v1 EC-Rest plugin.
-
Delete the property
/server/ec_customEditors/pickerStep/Rest - Run Rest
. -
Clear your browser’s cache.
-