The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/deploy-tar-extract-failure has failed. Run started by GitHub user chennaji9 (triggered by chennaji9).
Head commit for run: 9624a3d2ae39519e55dbfc1c24faf018e57c0e5b / healthy boy <[email protected]> fix(deploy): stop the deployment when source extraction fails The upload_source remote command separated its phases with semicolons and ended with "|| true", so a failed tar extraction exited 0: the deploy continued with a wiped, partially extracted tree and only failed much later in the docker build, far from the root cause. The stale-tree wipe also left the preserved deploy/.env only as the /tmp backup copy, because the restore mv could not target a directory the failed extraction never recreated. Chain every phase with && instead: a failed .env backup, wipe, extraction, or restore now exits the remote command non-zero and the set -e deploy script stops at the failing step. On extraction failure the restore still runs first and the /tmp backup survives for the next run, so the environment-specific configuration is never silently lost. Verified by replaying the exact remote command string against a fake remote directory: corrupt tarball exits 2 with the new chain (old chain exits 0 and proceeds); healthy tarball behaves identically to before (exit 0, .env restored, archive removed). Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37956641847 With regards, GitHub Actions via GitBox
