Additional SSH command phase
There should be a SSH command phase that combines “Before Release Link” and “After Changes” that works across regular and zero-downtime servers.
There should be a SSH command phase that combines “Before Release Link” and “After Changes” that works across regular and zero-downtime servers.
Log in to comment and vote
Comments5
James Fenwick
Jun 5, 2025
This along with path and release_path matching would allow me to have one set of SSH commands that would with across server types.
Facundo@DHQ
Jun 10, 2025
Hello @James Fenwick,
Can you please explain what's the current use case that's not supported? Why not just use the After Changes?
Thank you!
James Fenwick
Jun 10, 2025
Hi,
For example I want to install Composer dependencies in a PHP project.
If I used “After Changes” it would run after the release directory was linked, risking downtime.
Facundo@DHQ
Jun 10, 2025
Okay, and why aren't you using the Build Pipeline for that?
James Fenwick
Jun 10, 2025
I don’t really want to transfer an additional ~500MB from the build server.
Another example of a command that I would run in the same hypothetical phase would be database migrations, which would need to be on the server to run anyway.