Display build artifacts on tags page if the tag was pushed after the commit build

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

• Close this issue

Description

In my company, we disabled the CI builds on tags, using the except feature in the .gitlab-ci.yml file. This way, we can release some internal versions on the master branch, but the QA only takes the tagged builds. We don't have to recompile the software too (it takes several minutes, with quite large C++ sources, and multiple variants).

On the tags page, we write the changelog, so it's easy to read the changes and download the artifacts (and the QA can bookmark only this page).

Proposal

Allow build artifacts aliases. The way it should work is the following:

• Disable build on tag (using except filter in gitlab-ci.yml).
• Trigger a build on a branch, wait for the build to complete.
• Tag the commit associated with this build (according to the except config, it doesn't trigger a build).

Expected

• The build artifacts are available, since it's the same commit ; just with a tag.

Current behavior

• The tag has no available artifacts.