Files
neil f5f2242d60 deploy/ssh: stop the batched remote command at the first failed step
In single-call mode (the default) all steps were joined with ";", so a
failed write did not stop the batch: the remaining files were still
overwritten, DEPLOY_SSH_REMOTE_CMD still ran on the broken file, and the
deploy reported success because only the last exit code counted.

With a POSIX remote shell, steps are now wrapped in { } and joined with
&&, matching multi-call mode. Non-POSIX remote shells (powershell -c,
cmd /c) keep the old ";" join byte for byte.

See #7328
2026-10-14 14:13:21 +08:00
..
2026-07-17 12:38:14 +08:00
2024-04-07 12:36:19 +00:00
2021-03-30 09:18:33 +02:00
2021-05-07 12:12:30 +02:00
2017-02-19 20:40:53 +08:00
2024-04-07 12:36:19 +00:00
2024-10-13 17:41:22 +02:00
2022-11-23 21:33:29 +08:00
2026-09-04 15:27:35 +08:00
2026-09-19 15:43:23 +02:00
2018-03-22 13:45:43 -04:00
2025-10-21 11:34:46 +02:00
2021-09-04 16:59:50 +08:00
2026-09-04 15:27:35 +08:00
exe
2017-02-05 23:14:25 +08:00
2017-02-19 20:40:53 +08:00
2024-04-07 12:36:19 +00:00
2017-02-19 20:40:53 +08:00
2017-02-19 20:40:53 +08:00
2021-01-13 20:37:05 +00:00
2017-02-19 20:40:53 +08:00
2020-01-30 12:06:39 +08:00
2026-06-19 14:23:03 +02:00
2025-12-19 18:12:45 +03:00
2026-09-11 11:55:38 +08:00
2024-12-31 18:04:39 +01:00
2025-11-08 16:59:10 -05:00
2022-12-28 02:47:49 +08:00
2025-04-18 00:25:10 +02:00
2024-10-13 17:41:22 +02:00