## Issue description <!--Title this issue: `FY27Q2 Stage Lead planning issue: Verify`--> This issue outlines the themes that will be the focus of the `Verify` stage lead during `Q2` of `FY27`. Legend: - :hourglass_flowing_sand: : Waiting for `<...>`. `technical writer`, or `PM input`, or `Engineering input` - :construction: : In progress - :white_check_mark: : Complete - :lifter_tone3: : Stretch goal (add next to any item that is aspirational this quarter) ### Themes This planning issue breaks down the themes into four categories: - Pipeline configuration: Pipeline workflow, configuration, and troubleshooting. - Testing and reports: Code coverage reporting and visualization. - Docker and container jobs: Building Docker images without privileged mode in CI/CD. - Runner: Clarify executor usage and compatibility. #### Pipeline configuration - Short description: Improve documentation for pipeline configuration options and consolidate CI/CD limits. - Reasoning: Provide guidance on implementing effective pipeline workflows, policies, and resolving common issues. | Issue | Group(s) | Status | Effort | Priority | Details | |-------|----------|--------|--------|----------|---------| | https://gitlab.com/gitlab-org/gitlab/-/issues/557974+ | ~&quot;group::pipeline authoring&quot; | :hourglass_flowing_sand: Waiting for TW | Medium | Medium | Led by: `@marcel.amirault` <br><br>Revise the CI/CD [inputs](https://docs.gitlab.com/ci/inputs/) documentation page to improve clarity, organization, and user experience. | | https://gitlab.com/gitlab-org/gitlab/-/issues/560228+ | ~&quot;group::pipeline execution&quot; | :white_check_mark: | Medium | High | Led by: `@marcel.amirault` <br><br>Consolidate CI/CD limits documentation. | #### Testing and reports - Short description: Improve documentation for code coverage reporting and visualization features. - Reasoning: Clarify the distinction between coverage reporting and visualization, improve troubleshooting guidance, and improve cross-referencing between related YAML keywords. | Issue | Group(s) | Status | Effort | Priority | Details | |-------|----------|--------|--------|----------|---------| | https://gitlab.com/gitlab-org/gitlab/-/issues/578763+ | ~&quot;group::pipeline execution&quot; | :white_check_mark: | Medium | Medium | Led by: `@lyspin` <br><br>Clarify the distinction between coverage reporting (percentages in MR widget) and coverage visualization (line-by-line diff annotations). Improve JaCoCo/Cobertura docs, add troubleshooting guidance, and improve cross-referencing between related YAML keywords. | #### Docker and container jobs - Short description: Update documentation for secure Docker image building approaches in CI/CD. - Reasoning: Provide security-focused guidance on building Docker images without privileged mode. Includes restructuring the main Docker build page for improved navigation and decision guidance (CTRT principles). | Issue | Group(s) | Status | Effort | Priority | Details | |-------|----------|--------|--------|----------|---------| | https://gitlab.com/gitlab-org/gitlab/-/issues/549941+ <br>+<br> https://gitlab.com/gitlab-org/gitlab/-/work_items/572671+ | ~&quot;group::pipeline execution&quot; | :white_check_mark: | Medium | High | Led by: `@lyspin` <br><br>Address rootless build documentation and validation issues following Kaniko removal. | | https://gitlab.com/gitlab-org/gitlab/-/issues/546511+ | ~&quot;group::pipeline execution&quot; | :hourglass_flowing_sand: Waiting for TW | Medium | Medium | Led by: `@rsarangadharan` <br><br>Add secure CI/CD variable handling documentation to BuildKit examples. Follow-up from Marcel's security concerns about variable masking and protected variables. | | https://gitlab.com/gitlab-org/gitlab/-/issues/581635+ | ~&quot;group::pipeline execution&quot; | :white_check_mark: | Medium | High | Led by: `@rsarangadharan` <br><br>Restructure "Use Docker to build Docker images" page to apply CTRT principles and improve user navigation. Address user feedback about page complexity by adding decision guidance and using tabs for configuration variations. | #### Runner - Short description: Document Runner executor usage and compatibility. - Reasoning: Provide clear guidance on executor support status, feature compatibility, and migration paths for deprecated executors. | Issue | Group(s) | Status | Effort | Priority | Details | |-------|----------|--------|--------|----------|---------| | https://gitlab.com/gitlab-org/gitlab-runner/-/work_items/39342+ | ~&quot;group::runner core&quot; | :white_check_mark: | Medium | High | Led by: `@rsarangadharan` <br><br> Document which Runner executors are actively developed, in maintenance mode, or deprecated, along with their feature compatibility. | ### ⚡ Quick wins - Short description: Easy docs fixes and improvements across the stage docs. - Reasoning: While it's important that big cross-stage improvements are planned and tracked, it's also important to recognize small but significant improvements. 1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/232768+ 1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/232513+ 1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/233885+ 1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/235949+ 1. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/236318+ ### Retrospective After the quarter is complete, create discussion threads with the following titles. Use these discussion threads for self-reflection and to note feedback from others about how the quarter went. ```md ## 👍 What went well? ``` ```md ## 👎 What didn't go as well? ``` ```md ## 📈 What could be improved for next time? ``` ### Ongoing tasks Manage TW-DRI assignments for all milestones: <!--- [Create issue board](https://gitlab.com/groups/gitlab-org/-/boards/2159734?label_name[]=devops%3A%3Acreate) - [Plan issue board](https://gitlab.com/groups/gitlab-org/-/boards/7825333) - [Secure issue board](https://gitlab.com/gitlab-org/gitlab/-/boards/7602348?label_name[]=devops%3A%3Asecure) - [Verify issue board](https://gitlab.com/groups/gitlab-org/-/boards/7318948?label_name[]=devops%3A%3Averify&label_name[]=documentation)--> Specific [TW milestone planning issues](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/issues/?sort=created_date&state=opened&search=milestone%20plan&in=TITLE): - [x] [19.0](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1630). Release date: 2026-05-21 - [x] [19.1](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1651). Release date: 2026-06-18 - [x] [19.2](https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1660). Release date: 2026-07-16 ### References - [Stage leads](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#stage-leads) - Previous issue: https://gitlab.com/gitlab-org/technical-writing/team-tasks/-/work_items/1575