Persistent SSH sessions in your pipelines. SHA-256 verified deployments. Works with GitHub Actions, GitLab CI, and any runner that can execute shell commands.
CI/CD pipelines need to deploy to remote servers. Every pipeline step creates a new SSH connection. Credentials are stored as secrets but end up as environment variables in the runner. There is no built-in integrity verification — a compromised runner could deploy modified artifacts without detection. No manifest of what was actually deployed.
Install sshDCommander in your CI runner. Start the daemon once at the beginning of the pipeline. All subsequent steps reuse the persistent SSH session. Deploy with --manifest for SHA-256 verification. The --client-id links every operation to the pipeline run.
Start the daemon once. Every pipeline step reuses the same SSH connection. No reconnect overhead between steps.
Every file uploaded with SHA-256 verification. Deploy manifests record exactly what was deployed. Post-deploy verification catches compromised artifacts.
The -s flag handles pipes, quotes, and variable expansion safely. No more escaping nightmares in YAML pipeline definitions.
Use --client-id github-actions-123 to link every operation to the specific pipeline run. Full traceability.