actions-marketplace-validations/Upload a Build Artifact via FTP(S) Protocol
Upload a build artifact that can be used by subsequent workflow steps
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Mar 9, 2023
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/sokuhatiku_ftp-upload-artifact@29fe15de30b7a25d5a4b5c09cfddd22a98a0fcb2 # no releases — HEAD as of 2026-07-12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| name | Artifact name | — | artifact |
| path | A file, directory or wildcard pattern that describes what to upload | yes | — |
| if-no-files-found | The desired behavior if no files are found using the provided path. Available Options: warn: Output a warning but do not fail the action error: Fail the action with an error message ignore: Do not output any warnings or errors, the action does not fail | — | warn |
| retention-days | Duration after which artifact will expire in days. 0 means using default retention. Minimum 1 day. Maximum 90 days unless changed from the repository settings page. | — | — |
| host | FTP server host | yes | — |
| port | FTP server port | no | 21 |
| username | Username for FTP access. Defaults to anonymous if not provided | no | anonymous |
| password | Password for FTP access. Defaults to anonymous if not provided | no | anonymous |
| secure | Use ftps protocol. | no | true |
| remote-path | Remote root directory to store artifacts. Defaults to root directory if not provided. If the path does not exist, it will be created. If possible, change the server-side user home directory instead of using this option. | no | / |
Outputs
no outputs