Do not upload Linux/macOS debug build packages as CI artifacts
Table of Contents
This page is a capture in the next bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
The continuous-linux.yml and continuous-macos.yml workflows'
"Upload a Build Artifact" step runs for every matrix.buildtype,
including debug, uploading the built .deb=/.dmg= package
regardless of build type. Skip the artifact upload for debug builds
— gate the step (e.g. if: matrix.buildtype ! 'debug'=) so only
release-type packages get uploaded. Debug packages carry full debug
symbols and are far larger than release packages, for no real
consumer benefit (nobody downloads a CI debug package to install
it — it exists for developers to grab intermediate build state, if
at all).
Why
Debug-build packages are very large and cost storage/transfer for artifacts nobody actually consumes as installables; only the release packages are meant for end users to download and run.
References
.github/workflows/continuous-linux.yml:276-280("Upload a Build Artifact" step).github/workflows/continuous-macos.yml(equivalent step)