Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,874
    • Issues 35,874
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,262
    • Merge Requests 1,262
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #262725

Closed
Open
Opened Oct 02, 2020 by Phil Calder@pcalderDeveloper

GitLab API endpoint to return defined SaaS experiments using experimentation.rb

Expose defined experiments and status on GitLab.com using the existing experimentation.rb in an API endpoint.

  1. experiment key
  2. status (active or not - we don't need percentages, groups, etc at this stage).
  3. 'relatively' up to date (caching for hours, but less than a day, is acceptable).

A production ready version of:

experiment_statuses = []
Gitlab::Experimentation::EXPERIMENTS.each do | experiment_config |
  # Feature.get(experiment[0]).percentage_of_time_value > 0
  experiment_key = experiment_config[0]
  experiment_statuses << { key: experiment_key, enabled?: Gitlab::Experimentation.enabled?(experiment_key) }
end
experiment_statuses.to_json

In the first instance, consumers of this endpoint are GitLab Team Members (support, SREs, development, product).

Edited Oct 18, 2020 by Phil Calder
Assignee
Assign to
13.5
Milestone
13.5 (Past due)
Assign milestone
Time tracking
Oct 30, 2020
Due date
Oct 30, 2020
Reference: gitlab-org/gitlab#262725