Distinguish between technical build artifacts and artifacts downloadable via UI

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Use case

The results of a build stage are interesting for testing not yet merged code - just download the .exe, .apk, ... whatever your executable is and see/test the patches for yourself. So it is awesome that you can download build artifacts via the UI 👍

However, the other >300 files and 800 MB build artifacts (gross exaggeration by me 😄 ) used by the following CI stages to speed up builds and tests are of lesser interest to be downloaded via the UI by a human.

Proposal

Offer a filter functionality to filter out artifacts which are not to be served via the UI download button. Similar how the test reports are declared as artifact but not included in the artifacts downloaded via the UI.

P.S.: Maybe, different expiration dates would also be interesting here: Several weeks for the executables and only several hours for the technical artifacts. So would it make sense to make a list out of the artifacts entry?