Allow exposed artifacts while review app is running
Problem to solve
The exposed artifacts in a merge request do not appear in the web UI while a review app is running.
The review app needs to be stopped for the
artifacts:expose_as artifacts to be displayed.
When an artifact is created that is needed in order to use the review app, there is no easy way to expose it to the developers.
In my current use case, the artifact being exposed is the instructions/configuration file required to connect to the deployed server(s).
Sasha, Simone, and Devon would be the biggest user of this feature.
User experience goal
The user should be able to access the exposed artifacts for any completed job, in the merge request UI, before the whole pipeline is completed.
Permissions and Security
Availability & Testing
What does success look like, and how can we measure that?
The user is able to access the exposed artifacts for any completed job, in the merge request UI, before the whole pipeline is completed.