Page MenuHomePhabricator

Infer schema_id from the selected stream_name via Test Kitchen poller
Closed, ResolvedPublic2 Estimated Story Points

Description

Description

Now that we are encouraging teams to use base streams and GrowthBook UI is only offering those ones when registering an experiment, it makes sense to remove schema_id as a custom field. That value can be inferred from the selected stream_name + the current version (where we are not expecting changes).

Acceptance criteria

  • stream_id Custom Field has been removed from GrowthBook UI
  • The schema_id for an experiment has been set before being added to experiments_cache. The value is based on the selected stream_name + the current version for that stream
  • The Custom Field in GrowhtBook UI, where schema_id is chosen, has been removed

Event Timeline

Sfaci updated the task description. (Show Details)
Sfaci updated the task description. (Show Details)
Sfaci set the point value for this task to 2.Jul 1 2026, 4:09 PM

I'm probably forgetting the context for this ticket - are we sure we don't want to support custom schema ids? it seems like if the base schemas for whatever reason don't capture enough info, that we would still want to enable product teams to use custom schemas for edge cases?

I'm probably forgetting the context for this ticket - are we sure we don't want to support custom schema ids? it seems like if the base schemas for whatever reason don't capture enough info, that we would still want to enable product teams to use custom schemas for edge cases?

Yes, you are fully right. But it seems that we expect very few changes and the general case would be just using the base streams/schemas. The stream_name Custom Field in GB was already set like a closed list where only product_metrics.web_base and product_metrics.app_base are the possible values. Of course, when needed, we could update and add new streams/schemas. But also, I do remember we talked about encouraging people to use base streams/schemas so this decision would be pretty aligned with that.

For more context, this is the conversation where were we discussed it

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)
  • variation ids must be changed from the default integers

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)
  • variation ids must be changed from the default integers

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)
  • variation ids must be changed from the default integers

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Your experiment phuedx-test-T430795 failed validation and its status has been reverted to draft in GrowthBook.

Validation errors:

  • Start Date must fall on a deployment day (Mon–Thu)

Change #1319178 had a related patch set uploaded (by Clare Ming; author: Clare Ming):

[operations/deployment-charts@master] Test Kitchen UI: Deploy v1.5.0 release to staging

https://gerrit.wikimedia.org/r/1319178

Change #1319178 merged by jenkins-bot:

[operations/deployment-charts@master] Test Kitchen UI: Deploy v1.5.0 release to staging

https://gerrit.wikimedia.org/r/1319178

Change #1321827 had a related patch set uploaded (by Clare Ming; author: Clare Ming):

[operations/deployment-charts@master] Test Kitchen UI: Deploy v1.5.2 release to production

https://gerrit.wikimedia.org/r/1321827

Change #1321827 merged by jenkins-bot:

[operations/deployment-charts@master] Test Kitchen UI: Deploy v1.5.2 release to production

https://gerrit.wikimedia.org/r/1321827