Reduce output in deploy.yml #389

Closed
opened 2026-06-04 00:03:36 +00:00 by guettli · 1 comment
guettli commented 2026-06-04 00:03:36 +00:00 (Migrated from codeberg.org)

The output in deploy.yml is way too long.

Reduce the output.

The Dagger output is not needed. Is there a way to remove it, except for errors?

See https://codeberg.org/guettli/sharedinbox/actions/runs/1472/jobs/2/attempt/1

The output in deploy.yml is way too long. Reduce the output. The Dagger output is not needed. Is there a way to remove it, except for errors? See https://codeberg.org/guettli/sharedinbox/actions/runs/1472/jobs/2/attempt/1
guettlibot commented 2026-06-04 00:30:03 +00:00 (Migrated from codeberg.org)

The PR is open at https://codeberg.org/guettli/sharedinbox/pulls/390.

What I did: The three Dagger-based deploy tasks in Taskfile.yml (deploy-linux, publish-android, deploy-apk) were producing verbose output in CI even on success. I wrapped each dagger call with the existing scripts/silent_on_success.sh helper, which captures all output to a temp file, discards it on success, and only replays it when the command fails. This is the same pattern already used throughout the project for other noisy commands (fvm install, flutter pub get, build_runner, etc.).

The PR is open at https://codeberg.org/guettli/sharedinbox/pulls/390. **What I did:** The three Dagger-based deploy tasks in `Taskfile.yml` (`deploy-linux`, `publish-android`, `deploy-apk`) were producing verbose output in CI even on success. I wrapped each `dagger call` with the existing `scripts/silent_on_success.sh` helper, which captures all output to a temp file, discards it on success, and only replays it when the command fails. This is the same pattern already used throughout the project for other noisy commands (`fvm install`, `flutter pub get`, `build_runner`, etc.).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: guettli/sharedinbox#389