Exposed artifacts do not become available until after pipeline is done
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=217996) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The recent `artifacts.expose_as` property is great, and allows developers to link to e.g. Code Coverage and other reports much easier. But unfortunately the list of artifacts to not become available until the pipeline completes. This is a big drawback is it prevents feedback from being received as results come in, and forces us to wait until all jobs run to completion. This can be compared to the environment section in the same widget, which shows all environments directly, and is updated with app links as soon as the connected job completes. ### Steps to reproduce 1. Create a MR for a projects that uses `expose_as` 2. Trigger a new pipeline for MR 3. Before the pipeline completes, check the Pipeline widget ### Example Project Can't really show this in a project, since pipelines will eventually be completed. ### What is the current *bug* behavior? "View X artifacts" becomes visible when pipeline completes ### What is the expected *correct* behavior? "View X artifacts" should be shown as soon as a job completes ### Relevant logs and/or screenshots #### Before pipeline completion ![Before pipeline completes](/uploads/91366c5813454857ea50f6cf6aced447/image.png) #### After pipeline completion ![After pipeline completes](/uploads/3db00126b5a46dc76c4ada008cc90217/image.png) ### Output of checks This bug happens on Gitlab.com
issue