Fix exposing artifacts with dot slash paths
What does this MR do and why?
Resolves #419627 (closed)
When artifact paths specified in the CI config starts with the ./ prefix, the pattern matching for metadata entries don't work properly. This fixes the bug to make sure that we always use the path stripped off of the prefix.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Screenshot based on the CI config from eb-tests/test-expose-as!1.
Before | After |
---|---|
How to set up and validate locally
- Clone the test project from eb-tests/test-expose-as!1, and open the same MR so you can test the exposed artifacts.
- As seen on the screenshot, the
build-artifacts-2
should show up even though all its artifact paths include the./
prefix. - Then click on the
my artifacts
link forbuild-artifacts-2
and it should redirect you to the browse page. There should be all the artifacts there namelyhello_dot_1.txt
andhello_dot_2.txt
.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.