Features/migration cyberduck release windows chocolatey

[RaveenaRamany]

Migration Jenkins-Pipeline Cyberduck-Realese-Windows-Chocolatey

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ylangisc]

Do we need all these exclusions? Are the 3 includes above not sufficient?

[ylangisc]

Same question here with all the excludes. If not necessary the entire transfer task and ssh setup could be simplified using https://github.com/appleboy/scp-action.

[dkocher]

It would be nice if we can dogfood Cyberduck CLI here. We have a Cyberduck CLI Github Action ¹ to transfer artifacts. Documentation can be found in the README ² and sample usage in our connection profiles synchronization with S3 ³.

@AliveDevil May assist here when in doubt.

Footnotes

1. https://github.com/iterate-ch/cyberduck-cli-action ↩

2. https://github.com/iterate-ch/cyberduck-cli-action/blob/main/README.md ↩

3. https://github.com/iterate-ch/profiles/blob/main/.github/workflows/profiles-sync.yml ↩

[ylangisc]

maven.iterate repositories not necessary for Cyberduck builds.

[ylangisc]

Needs to be reverted before merge.