Fix Gitea deploy paths for act_runner without run_attempt.
Deploy Ladill Meet / deploy (push) Successful in 46s

Use gitea.run_id only for WORKSPACE and RELEASE_ARCHIVE temp paths.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
isaacclad
2026-06-30 23:55:43 +00:00
co-authored by Cursor
parent ebb619e034
commit 3348d418b8
+4 -3
View File
@@ -19,8 +19,9 @@ jobs:
env:
NODE_ROOT: /tmp/ladill-node-22-r1
NODE_VERSION: "22.14.0"
RELEASE_ARCHIVE: /tmp/ladill-meet-release-${{ gitea.run_id }}-${{ gitea.run_attempt }}.tgz
WORKSPACE: /tmp/${{ gitea.repository_owner }}-meet-${{ gitea.run_id }}-${{ gitea.run_attempt }}
# act_runner v0.2.x does not expose gitea.run_attempt — use run_id only.
RELEASE_ARCHIVE: /tmp/ladill-meet-release-${{ gitea.run_id }}.tgz
WORKSPACE: /tmp/${{ gitea.repository_owner }}-meet-${{ gitea.run_id }}
LADILL_APP_ROOT: /var/www/ladill-meet
steps:
- name: Checkout
@@ -78,7 +79,7 @@ jobs:
- name: Deploy release
shell: bash {0}
env:
LADILL_RELEASE_ARCHIVE: /tmp/ladill-meet-release-${{ gitea.run_id }}-${{ gitea.run_attempt }}.tgz
LADILL_RELEASE_ARCHIVE: /tmp/ladill-meet-release-${{ gitea.run_id }}.tgz
run: |
set -Eeuo pipefail
: "${LADILL_APP_ROOT:?Set LADILL_APP_ROOT}"