## CI Translation Components Production Rollout Trial Trial window: **May 18 → July 1, 2026** ### Vision Make translation delivery through GitLab repeatable, low-touch, and production-safe, so customers can adopt standardized translation workflows *inside the platform they already use*. For v1, we are not solving every localization use case. We are proving that a CI translation component can reliably handle a small, well-bounded set of **real production content**, create the right translation merge requests automatically, and establish the foundation needed to expand this into something customers can adopt more broadly. We build something customers can use by using it ourselves. Reference: [CI Translation Components](https://gitlab.com/gitlab-com/localization/ci-translation-components) · 2026 AI Enterprise Hackathon ([slides](https://docs.google.com/presentation/d/1ujBKn4ZX8vBntXzKKMJN6zsuOiZSTG6UO76tf4golrI/edit?usp=sharing), [video](https://drive.google.com/file/d/1EfWV8Hq8_rzvL0f6-ZhREfJhF6dI1zSl/view?usp=drive_link)). ### Goal / Outcome By **2026-07-01**, we have: - CI Translation Components running in production on real projects. - A documented, repeatable workflow from request → CI execution → translation MR → review → merge. - Clear ownership, monitoring, and support paths for these components. ### Scope: First production wave 1. **about.gitlab.com — Spanish Solutions pages** - [`content/en-us/solutions`](https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/tree/main/content/en-us/solutions?ref_type=heads) — 44 pages across 7 categories. 2. **GitLab Operator docs — Korean, French, Japanese** - [`gitlab-operator/doc`](https://gitlab.com/gitlab-org/cloud-native/gitlab-operator/-/tree/master/doc?ref_type=heads) — 11 pages, excluding `/developer`. ### Roadmap #### Phase 1 — Blind Spot Identification (by May 18) Two parallel workstreams surface gaps before production rollout: - [#728](https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/728) — Continuous localization of `content/es/solutions` on the about-gitlab-com fork. - [#736](https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/736) — Continuous localization of `/docs` on the Operator test fork. **Prerequisite (by May 18):** [#726](https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/726) — Provision group-level `AI_API_KEY` and `GITLAB_API_TOKEN` to unblock all production pipelines. #### Phase 2 — Production Rollout (by May 29) - CI Translation Components added to production for **about.gitlab.com**. - CI Translation Components added to production for **Operator**. #### Phase 3 — Full Operational Coverage (by June 26) - Continuous translation of Spanish Solutions pages live on about.gitlab.com. - Continuous translation of `/docs` live in [gitlab-operator](https://gitlab.com/gitlab-org/cloud-native/gitlab-operator). ### Architecture (about.gitlab.com flow) Source change → detect → translate (via GitLab AI Gateway) → commit → MR → auto-merge. Linguistic review is **adjacent, not blocking** — it fires after merge via the Translation Review Flagger flow, creating async tracking issues in `linguistic-review-tracker`. All model calls go through GitLab AI Gateway; **no direct vendor API calls** from the runner. See the [flow diagram on #730](https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/730#note_3317655643). ### Success metrics (tracked from July 1) - **Pipeline success rate:** ≥ 50% of production translation runs complete without manual engineering intervention. - **MR creation success rate:** ≥ 80% of successful runs produce the expected MR automatically. - **Turnaround time:** median request → MR created within **1 business day** for source updates (stretch: minutes). ### Security & compliance readiness checks - **Least-privilege access** for the component and any service accounts / tokens; secrets masked and hidden. - **Auditability:** every run traceable from request → pipeline → MR. - **Rollback / disable path:** can be turned off immediately, with the procedure known to all DRIs. ### Post-July 1: Runbooks & docs Enable any GitLab customer to drop CI Translation Components into their workflows: 1. How to adopt the CI Translation Component. 2. How to troubleshoot failed jobs. 3. How to request or contribute changes. ### DRIs | Area | DRI | |------|-----| | Overall | @laurenbarker | | Linguistic Quality Assurance (LQA) | @mjsibanez | ### Related - Roadmap source: [#730](https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/730) - Infra prerequisite: [#726](https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/726)