Skip to content

Rebrand Verify:Testing into Verify:Pipeline Insights

Jackie Porter requested to merge jreporter-master-patch-69439 into master

Overview

As I interview users of our Testing features and capabilities I began to notice a trend in the language they were using and would like to uplevel the focus for the Testing group to be more about ensuring pipelines are identifying problems and providing visibility into potential mitigations for problematic code changes or pre-production readiness. The purpose of testing software before changes are released is to mitigate the risk of changes to the end-users, the companies reputation, and the software development lifecycle. Many of the reasons for testing for performance, accessibility, coverage, and managing the latest artifacts is to control the blast radius of changes to the code base.

Why Pipeline Insights?

The Testing Group has been very focused on increasing visibility into project quality and coverage for the Director Personas, which are the team members in their organization responsible for responding to problems introduced as a result of code changes. Visibility to code changes via the merge request widget and reports including the request to block changes to code if the changes do not meet certain thresholds are great examples of work the team has been delivering to help our customers and users manage the safety of their code changes.

More recently, the inclusion of Build Artifacts and the strategy to make managing artifacts easier and more seamless to help organizations navigate retention policies as well as a budget risk due to the consumption pricing nature of storage is better included with a team focus on managing the greater visibility into code change impacts on software.

Additionally, an emerging trend in the market is supply chain security as a result of increasing political pressure to improve security in software practices. Pipelines are one of our biggest areas of opportunity to improve visibility into the secure supply chain processes across GitLab and could see the charter of this group enabling better reporting and visibility into build/job artifacts for SBOM.

Proposal

Rename Testing Group to Pipeline Insights Group

Approvals

Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

  • VP, Product @david
  • The Product Director relevant to the stage group(s) @kencjohnston
  • The Engineering Director relevant to the stage group(s) @sgoldstein
  • Director of Product Design @vkarnes
  • CEO

The following people need to be on the merge request so they stay informed:

  • Chief Technology Officer @edjdev
  • Vice President of Development @clefelhocz1
  • Vice President of Quality @meks
  • Vice President of User Experience @clenneville
  • The Product Marketing Manager relevant to the stage group(s)
  • Senior Manager, Technical Writing @susantacker

After Approvals and Merge

Edited by Jackie Porter

Merge request reports