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

Remote Access plugin release notes

1 minute readExtensibilityDeveloper productivity

2.1.0

  • Upgraded dependencies.

  • Migrated to Java 17 and Groovy 3.

    Because of the Java versions supported by CloudBees CD/RO, you can only use EC-RemoteAccess v2.1.0 with CloudBees CD/RO agents v10.11 and later.

2.0.0

  • Ported plugin to PDK.

  • Added usage of new configurations.

1.2.6

  • Updated logger.

1.2.5

  • Updated dependencies.

1.2.4

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

1.2.3

  • Updated logger to slf4j.

1.2.2

  • Renamed to "CloudBees CD/RO".

1.2.1

  • Fixed Plugin Dependency Management to work with gateways.

1.2.0

  • Added the option to check the connection when creating or editing a configuration.

  • Fixed issues in the RunCustomCommand procedure when the Flow agent runs on Java 11.

1.1.0

  • Provisioning of binary dependencies (for example, Grape jars) in the agent resource is now delivered through a new mechanism called Plugin Dependency Management. Now, binary dependencies are seamlessly delivered to the agent resource from the Flow Server when a new version of a plugin is invoked for the first time. The Flow Repository setup is no longer required for this plugin.

1.0.1

  • Renamed to "CloudBees CD".

1.0.0

  • First release.

Known issues

  • When the Run Custom Command procedure is executed in interactive mode, the plugin cannot distinguish between the command output versus errors in stdout. Consequently, both are reported in the remoteCommandOutput parameter and no warning is reported in the Job summary if errors are returned in stdout, even if the command otherwise succeeded.

  • During the connection check, if Interactivity information is specified incorrectly and a different Target user is used, it can lead to an endless connection check. In this case, a running job can be manually aborted.

Create Remote Access plugin procedures