Skip to content
GitLab Next
  • Menu
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 43,817
    • Issues 43,817
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,448
    • Merge requests 1,448
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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.org
  • GitLabGitLab
  • Issues
  • #216097
Closed
Open
Created Apr 29, 2020 by Marius Bobin@mbobin🔴Maintainer

Add application limits to Ci::InstanceVariable

In !30156 (merged) we are adding global (instance level) variables for CI jobs.

We should add an upper limit of 25 on the number of variables that can be defined, because:

  • these variables are loaded for each job
  • Our UI creates/updates them in bulk.

Add the limit behind a feature flag so if it does break someone on-prem they can disable the flag to resolve breakage.

Edited May 06, 2020 by Thao Yeager
Assignee
Assign to
Time tracking