Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #342882
Closed
Open
Issue created Oct 12, 2021 by David Fernandez@10io0️⃣Maintainer

GraphQL: remove the `pipelines` field from the package returned in the `version` field

🔥 Problem

Currently in GraphQL, we can query package -> versions -> pipelines. This currently pull an unbounded number of objects in memory.

🚒 Solution

After discussing with @nmezzopera, the pipelines field is not needed in the UI by the frontend. We could thus remove it from the package structures returned by the versions field.

Users wanting the get the pipelines of a given version, they still can query: package -> pipelines

⚠ Mind the deprecation process in GraphQL!

Assignee
Assign to
Time tracking