### Release notes Description: A complex CI configuration can be difficult to understand when trying to imagine how your pipeline might behave (or misbehave). Without a visual aid, it could be impossible to form a mental image of all the dependencies between countless jobs. In our first iteration of pipeline visualization, you can now see a graphic representation of your .gitlab-ci.yml file. Then you can decide for yourself if a picture really is worth a thousand words. https://docs.gitlab.com/ee/ci/yaml/README.html ### Problem to solve A `.gitlab-ci.yml` file can be difficult to understand, even for the original author if it is a complex CI configuration. Without a visualization of the pipeline that is created by a yml file, it could be hard to imagine how the pipeline might behave. ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * Any user trying to understand a CI yml file without running the pipeline ### User experience goal When a user is viewing (not editing) a CI yaml file in a [simple editor](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/.gitlab-ci.yml) they should have the option to see a graphic representation of the file. ### Proposal Translate the .gitlab-ci.yml file into a graphic visualization when viewing the static, checked-in file in the simple editor (https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/.gitlab-ci.yml). This first iteration of the feature is a view only representation with these elements: - From the static view of .gitlab-ci.yml file, add method for user to click to a graphical visualization of the file - Show stages and differentiate between stages with jobs and those without - Show jobs under the stage to which they belong - Show dependency between jobs (those using `needs` keyword) with a visual connecting line See **Design** section for most current illustrations. ### Further details This graph is built to replace the current pipeline graph eventually once it is prove to work well. There first effort to use thi graph as the new pipeline view is being made in a spike here: https://gitlab.com/gitlab-org/gitlab/-/issues/249094 ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html * [ ] Add expected impact to members with no access (0) * [ ] Add expected impact to Guest (10) members * [ ] Add expected impact to Reporter (20) members * [ ] Add expected impact to Developer (30) members * [ ] Add expected impact to Maintainer (40) members * [ ] Add expected impact to Owner (50) members --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change * Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements * If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes - yes, there should be unit test for new added logics * Integration test changes - yes, there should be frontend integration tests to make sure components are rendered * End-to-end test change - not required ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references Dovetail insight: https://dovetailapp.com/projects/4a4421a9-9fb4-4e16-acab-9ba9042e741d/insights/present/8704f88d-9b06-4ab1-987d-b21cc18e8f6d <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->