Skip to content

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 Screenshot_2023-12-05_at_1.26.49_PM

How to set up and validate locally

  1. Enable the FF global_ci_catalog
  2. Enable the FF ci_catalog_components_tab
  3. Run the rake task to generate catalog resources if needed: bundle exec rake "gitlab:seed:ci_catalog_resources[Twitter, 50]"
  4. Navigate to a CI project
  5. Go to Settings => General and make sure the project has a description
  6. Go to Build -> Tags and create a new tag
  7. Go to Deploy -> Releases and create a new release
  8. Navigate to Explore -> CI/CD Catalog
  9. Notice that you see Catalog resources
  10. Click on any resource
  11. Notice the components tab is present
  12. 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.

Related to #424967 (closed)

Edited by Frédéric Caplette

Merge request reports