## Summary Roll out [the feature](https://gitlab.com/gitlab-org/gitlab/-/issues/614009) currently behind the `vue3_migrate_ci_cd_analytics` feature flag. - DRI: @blabuschagne - Team Slack channel: `#g_optimize` > [!note] > Process and guidance live in the docs, this issue is just the commands and a place to track the rollout. > "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability. It is not the same as releasing the feature, which happens when the flag is removed. > [Feature flag controls](https://docs.gitlab.com/development/feature_flags/controls/) · [Feature flag lifecycle](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle) ## What could go wrong? The flag switches the Group CI/CD Analytics page from the Vue 2 bundle to the Vue 3 (`@vue/compat`) bundle. There is a single entrypoint, served by `Groups::Analytics::CiCdAnalyticsController#show`. If the page fails to render or a tab misbehaves under Vue 3, disable the flag to revert to the Vue 2 bundle. No data is written by this page, so the blast radius is rendering only. This page is already gated behind licensing independent of this flag: the controller returns a 403 for the whole page unless the group has at least one of the `group_ci_cd_analytics_pipelines` (Premium and Ultimate) or `group_ci_cd_analytics_releases` (Ultimate only) licensed features. The Pipelines tab additionally requires the pre-existing `group_ci_cd_analytics_pipelines_ff` flag (owned by group::ci platform, default disabled), and its dashboard has no panels wired up yet, so there is little to smoke test there beyond tab and filter plumbing. Questions: `#vue3_migration`. ## Rollout Run all production `/chatops` in [`#production`](https://gitlab.slack.com/archives/C101F3796) and cross-post the results to `#g_optimize`. Background: [incremental rollout process](https://docs.gitlab.com/development/feature_flags/controls/#process), [feature actors](https://docs.gitlab.com/development/feature_flags/#feature-actors). **Non-production** ``` /chatops gitlab run feature set vue3_migrate_ci_cd_analytics 50 --actors --dev --pre --staging --staging-ref /chatops gitlab run feature set vue3_migrate_ci_cd_analytics true --dev --pre --staging --staging-ref ``` **Production**: percentage rollout (wait ≥15 min between steps, watch dashboards): ``` /chatops gitlab run feature set vue3_migrate_ci_cd_analytics 25 --actors /chatops gitlab run feature set vue3_migrate_ci_cd_analytics 50 --actors /chatops gitlab run feature set vue3_migrate_ci_cd_analytics 100 --actors ``` Or target specific actors instead: ``` /chatops gitlab run feature set --user=blabuschagne vue3_migrate_ci_cd_analytics true ``` ## Before global rollout Confirm the relevant gotchas before going to 100%, see [enabling a feature for GitLab.com](https://docs.gitlab.com/development/feature_flags/controls/#enabling-a-feature-for-gitlabcom): - [Docs + version history](https://docs.gitlab.com/development/documentation/feature_flags/) updated - [Breaking changes](https://docs.gitlab.com/development/documentation/release_notes/#deprecations-removals-and-breaking-changes) announced, if any - [Change management issue](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#feature-flags-and-the-change-management-process) opened, if required - [External API consumers](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers) handled with a fail-open mechanism, if applicable ## Cleanup Remove the flag once [deemed stable](https://handbook.gitlab.com/handbook/product-development/how-we-work/product-development-flow/feature-flag-lifecycle/#feature-flag-lifecycle), see [cleaning up](https://docs.gitlab.com/development/feature_flags/controls/#cleaning-up). When removing the flag, also flip the `vue3_migration.yml` file to `status: migrated` and drop its `feature_flag` line: - `ee/app/assets/javascripts/pages/groups/analytics/ci_cd_analytics/vue3_migration.yml` Track it here, or open a follow-up [Feature Flag Cleanup issue](https://gitlab.com/gitlab-org/gitlab/-/issues/new?description_template=Feature%20Flag%20Cleanup). Remove the flag and its YAML definition from the codebase, then: ``` /chatops gitlab run release check <merge-request-url> <milestone> /chatops gitlab run feature delete vue3_migrate_ci_cd_analytics --dev --pre --staging --staging-ref --production ``` ## Rollback ``` /chatops gitlab run feature set vue3_migrate_ci_cd_analytics false # production /chatops gitlab run feature set vue3_migrate_ci_cd_analytics false --dev --pre --staging --staging-ref # non-production /chatops gitlab run feature delete vue3_migrate_ci_cd_analytics --dev --pre --staging --staging-ref --production # remove entirely ```