Update CI/CD catalog components tab with real data
What does this MR do and why?
Behind the disabled FF ci_catalog_components_tab
, we have the new components tab for the details page of a CI resource. Now that the API work is completed, we can remove the mock data and instead use the API. So this MR does not introduce the layout, but rather just adjust the data to match the real API structure.
Note also that the FF was not being pushed to the explore catalog yet, as this was initially developed for the namespace Catalog.
Screenshots or screen recordings
Before | After |
---|---|
Nothing, because the FF wasn't being pushed |
How to set up and validate locally
- Enable the FF
global_ci_catalog
- Enable the FF
ci_catalog_components_tab
- Run the rake task to generate catalog resources if needed:
bundle exec rake "gitlab:seed:ci_catalog_resources[Twitter, 50]"
- Navigate to a CI project
- Go to
Settings => General
and make sure the project has a description - Go to
Build -> Tags
and create a new tag - Go to
Deploy -> Releases
and create a new release - Navigate to
Explore -> CI/CD Catalog
- Notice that you see Catalog resources
- Click on any resource
- Notice the
components
tab is present - There are no visual issues and you can see all 3 columns of input data.
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 #424967 (closed)
Edited by Frédéric Caplette