## :fire: Problem Several ~GraphQL package related types have a `pipelines` field that returns a full featured pipeline object. Packages are linked to Pipelines through a Build Info object that is hidden completely by using a `has_many :pipelines, through: :build_infos` on the package objects. This situation brings several ~performance and scalability issues. Those issues are discussed in https://gitlab.com/gitlab-org/gitlab/-/issues/342881#note_747991561. The main pain point is that we can pull packages from a Project or a Group and this can pull many objects in a single ~GraphQL. ## :fire_engine: Solution The [plan](https://gitlab.com/gitlab-org/gitlab/-/issues/342881#note_747991561) is to properly map/return the Build Info objects in the ~GraphQL API. This would return the Pipeline ids (global id). Then, have a new ~GraphQL query that returns a Pipeline response given its global id. The ~frontend can then use those changes to get the pipelines and pull the Pipeline information in 2 ~GraphQL requests (one to get the package data, including the build info and one to get the pipeline data). By splitting this in two requests, we can introduce a loader for the pipeline data so that the first load will only need to execute the first request. ## :bar_chart: The Plan 1. 14.6 Mark `pipelines` fields as deprecated in the package related ~GraphQL types. https://gitlab.com/gitlab-org/gitlab/-/issues/347219. 1. 14.11 Add `build_infos` field to package related ~GraphQL types. https://gitlab.com/gitlab-org/gitlab/-/issues/347220 1. 14.11 Add a new ~GraphQL query to get Pipeline data given a global id. https://gitlab.com/gitlab-org/gitlab/-/issues/347221 1. 14.11 Update the Corpus management query. https://gitlab.com/gitlab-org/gitlab/-/issues/349159 1. 14.11 Announce the removals in the release post. https://gitlab.com/gitlab-org/gitlab/-/issues/347222 1. 14.11 Update corpus management to use `build_infos` field gitlab#349159 1. 15.0 Update the ~frontend to use (2.) and (3.) and stop reading the `pipelines` field. https://gitlab.com/gitlab-org/gitlab/-/issues/347223 1. 15.0 Remove the `pipelines` fields from the package related ~GraphQL types. https://gitlab.com/gitlab-org/gitlab/-/issues/347224