FileOps plugin release notes

2 minute readExtensibilityDeveloper productivity

4.0.1

  • Implemented internal improvements.

4.0.0

  • Plugin has been migrated from GWT to PDK.

3.0.1

  • Upgraded HttpClient library to v4.5.13.

3.0.0

  • Upgraded from perl-5.8 to perl-5.32. No backward compatibility with releases prior 10.3. Starting from this release new agent is required to run this plugin’s procedures.

2.1.1

  • Fixed the process the Move procedure uses to clean a destination folder if the source is a file.

2.1.0

  • The FileExists and DirectoryExists procedures have been improved. Control of how the procedure behaves was extended, and procedure set output properties/output parameters.

2.0.10

  • Fixed running Remote Copy - Native in pipeline context.

2.0.9

  • The documentation was migrated to the main documentation site.

2.0.8

  • Renamed to "CloudBees CD/RO".

2.0.7

  • Renamed to CloudBees.

2.0.5

  • Moved agent code to the plugin properties.

  • Fixed the Copy/Move procedures for paths that contain spaces.

  • Fixed the ListFiles procedure for paths that contain spaces.

  • Validate datetime parameter in UpdateLastTouch procedure.

  • Fixed SCP copying for paths that contain spaces.

  • Updated documentation for the Sync Folders procedure to clarify actions for rules.

  • Fixed a issue where the Remote Copy File (SCP) step failed on Linux with an ec-perl Command not found error.

  • Fixed Encrypt/Decrypt procedures running on Windows.

2.0.4

  • Renamed ElectricCommander to ElectricFlow.

2.0.3

  • Fixed documentation for the Remote Copy File (SCP) step.

2.0.2

  • Fixed link to help page.

  • Fixed issue for Create Zip file procedure for paths that contain spaces.

2.0.1

  • Several issues were fixed.

2.0.0

  • 22 new procedures were added.

  • Documentation was upgraded.

  • Use cases were added.

Known issues

  • For plugin v3.0.1 and earlier, when attempting to configure the Remote Copy-SCP procedure, if you select Credential  Browse button, the process freezes. In v4.0.0 and above, this issue was fixed.

    For plugin v3.0.1 and earlier, to configure a credential, you must be manually entered in the Credential field. The format for the path is:

    /projects/<your-project-name>/credentials/<your-credential-name>
    This credential must already exist in your project. If you need to create a new one, refer to Credential management.