Migrate "pipelines_artifacts" to GlDisclosure
requested to merge gitlab-community/gitlab:413460-pipeline-artifacts.vue-to-GlDisclosureDropdown into master
What does this MR do and why?
Migrates /app/assets/javascripts/pipelines/components/pipelines_list/pipelines_artifacts.vuefrom GlDropdown` to GlDisclosureDropdown
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
 |
videos
| Before | After |
|---|---|
| Screen_Recording_2023-07-12_at_11.30.15_AM | Screen_Recording_2023-07-12_at_11.21.57_AM |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
-
find or set up a project with a .gitlab-ci.yml configuration that generates artifacts
-
OR add this snippet of .gitlab-ci.yml to a project to generate an artifact:
make_artifact:
script: ["echo 'test' > file.txt"]
artifacts:
expose_as: 'artifact 1'
paths: ['file.txt']- create a branch and open an MR for it in the project
- run a pipeline for the branch/MR to generate the artifact file
- navigate to the MR (overview tab)
- the artifact dropdown should show up in the pipeline widget
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.
Related to #413460 (closed)
Edited by Frédéric Caplette