Skip to content

Update CI/CD catalog `versions` to use `latest_version`"

What does this MR do and why?

For performance reasons, we are deprecating the versions field on graphql type CiCatalogResources. Instead, we should use latest_version

Screenshots or screen recordings

No visual changes

Before After
Screenshot_2023-06-27_at_3.22.27_PM Screenshot_2023-06-27_at_3.22.27_PM

How to set up and validate locally

  1. Make sure you have an ultimate license for your GDK
  2. Enable the feature flag: ci_namespace_catalog_experimental
  3. Login as a user
  4. Create a few projects that you will be able to convert to Ci resources (ideally 20+).
  5. Once you have done so, get the ID of the first new project you wanted to convert. Then in Rails console, run:
projects = Project.where("id > ?", your_first_project_id)
projects.each do |project|
  project.update!(description: 'description')  
  ::Ci::Catalog::Resource.new(project_id: project.id).save   
end  
  1. Navigate to /$namespace/$project/-/ci/catalog/resources
  2. Notice that you can see "Unreleased" tag

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 #415497 (closed)

Edited by Frédéric Caplette

Merge request reports