A GitHub Action for securely copying files and artifacts to remote servers via SSH.
SCP Action is a GitHub Action that copies files and artifacts from GitHub Actions workflows to remote servers via SSH. It solves the problem of automating secure file deployments in CI/CD pipelines without requiring external tools or complex scripting. The action handles authentication, multi-server transfers, and cross-platform path conversions.
Developers and DevOps engineers using GitHub Actions for CI/CD who need to deploy build artifacts, static assets, or configuration files to remote servers (Linux or Windows) as part of their automation workflows.
Developers choose SCP Action for its native GitHub Actions integration, robust SSH support with proxy/jump host capabilities, and extensive configuration options. It eliminates the need for custom SSH scripts in workflows while providing security best practices and reliable file transfers.
GitHub Action that copy files and artifacts via SSH.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports simultaneous transfers to multiple remote hosts using a comma-separated list, streamlining deployment across server fleets without additional scripting.
Includes full proxy/jump host capabilities and both key and password authentication, handling complex network configurations reliably, as detailed in the proxy settings section.
Automatically converts paths for Windows servers and provides specific settings like `tar_dereference` for symlink support, reducing manual adjustments in mixed environments.
Seamlessly integrates with GitHub Actions artifacts and changed-files detection actions for efficient, incremental transfers, as shown in the usage examples.
Only operates on Linux Docker containers, preventing native use with macOS or Windows GitHub Actions runners, which restricts flexibility in heterogeneous CI/CD setups.
Requires additional setup on Windows servers, such as installing Git Bash and manual path adjustments, increasing configuration complexity and potential for errors.
Authentication failures are common due to key formatting issues, as noted in the FAQ, requiring careful PEM format management and troubleshooting in secrets.