pre-release build step fails: rsync not available in runner container #21

Closed
opened 2026-05-21 21:02:41 +00:00 by jmiller · 0 comments
Owner

Problem

The Build Package step in pre-release.yml.template uses rsync to copy src/ to the build directory. rsync is not always available in Gitea Actions runner containers, causing exit code 127 (command not found).

Root Cause

The runner container image does not include rsync. The step runs under bash -e so the missing command kills the entire job.

Fix

Replace rsync with cp -a which is universally available. Excluded files can be removed in a separate rm step.

Before:

rsync -a --exclude=... src/ build/package/

After:

cp -a src/. build/package/
cd build/package && rm -f sftp-config* .ftpignore *.ppk *.pem *.key .env* *.local .build-trigger && cd -

Affected Templates

  • pre-release.yml.template
  • Likely auto-release.yml.template

Discovered In

MokoWaaS repo pre-release workflow runs 9150, 9154.

## Problem The Build Package step in pre-release.yml.template uses rsync to copy src/ to the build directory. rsync is not always available in Gitea Actions runner containers, causing exit code 127 (command not found). ## Root Cause The runner container image does not include rsync. The step runs under bash -e so the missing command kills the entire job. ## Fix Replace rsync with cp -a which is universally available. Excluded files can be removed in a separate rm step. Before: ```bash rsync -a --exclude=... src/ build/package/ ``` After: ```bash cp -a src/. build/package/ cd build/package && rm -f sftp-config* .ftpignore *.ppk *.pem *.key .env* *.local .build-trigger && cd - ``` ## Affected Templates - pre-release.yml.template - Likely auto-release.yml.template ## Discovered In MokoWaaS repo pre-release workflow runs 9150, 9154.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/moko-platform#21