[Experiment Rollout] sast_entry_points - Test SAST entry points
What
Track the status of an experiment through to removal.
- Experiment key:
sast_entry_points
- Framework:
gitlab_experiment
- Feature flag name:
sast_entry_points
This is an experiment tracking issue for: gitlab-org/growth/team-tasks#376 (closed) using the scoped experiment label.
As well as defining the experiment rollout and cleanup, this issue incorporates the relevant
Feature Flag Roll Out
steps.
Owners
- Team:
group::activation
- Most appropriate slack channel to reach out to:
#g_activation
- Best individual to reach out to: @alexbuijs
- PM: @jstava
Expectations
What are we expecting to happen?
What might happen if this goes wrong?
What can we monitor to detect problems with this?
Tracked data
Measuring success
experiments
table
id | name |
---|---|
experiment_id | sast_entry_points |
experiment_subjects
table (note: we do not distinguish between the 3 variants in the database)
experiment_id | namespace_id | variant |
---|---|---|
experiment_id | namespace_id |
0 (control) or 1 (candidate) |
onboarding_progresses
table
namespace_id | security_scan_enabled_at |
---|---|
namespace_id |
NOT NULL (converted) or NULL (not converted) |
Snowplow tracking
The following events are tracked anonymously through Snowplow:
activity | category | action | context | sent from | variants |
---|---|---|---|---|---|
Visiting a project page | sast_entry_points |
assignment |
gitlab_experiment json schema | backend | control + banner + popover_light + popover_dark |
The button CTA is clicked | projects:show |
cta_clicked_button |
gitlab_experiment json schema | frontend | banner + popover_light + popover_dark |
The banner or popover is shown | projects:show |
show |
gitlab_experiment json schema | frontend | banner + popover_light + popover_dark |
The banner or popover is dismissed | projects:show |
dismissed |
gitlab_experiment json schema | frontend | banner + popover_light + popover_dark |
The banner or popover CTA is clicked | projects:show |
cta_clicked |
gitlab_experiment json schema | frontend | banner + popover_light + popover_dark |
Note: you can utilize CXL calculator to determine if your experiment has reached signifigance, it also includes an estimate for how much longer an experiment will need to run for before reaching signifigance.
Staging Test
Experiment tracking log
Experiment Results
Roll Out Steps
-
Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant stable counterpart in the Quality department) -
Enable on staging ( /chatops run feature set feature_name true --staging
) -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour ( /chatops run feature set --project=gitlab-org/gitlab feature_name true
) -
Coordinate a time to enable the flag with the SRE oncall and release managers - In
#production
mention@sre-oncall
and@release-managers
. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
- In
-
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set feature_name true
) -
Cross post chatops Slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel -
Announce on the issue that the flag has been enabled -
Remove experiment code and feature flag and add changelog entry - a separate cleanup issue might be required -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel -
Assign to the product manager to update the knowledge base (if applicable)
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set sast_entry_points false