Create communication plan for the running performance tests on GitLab MRs

Context

We are integrating Component Performance Testing (CPT) into our main pipelines to shift performance testing left to the MR level. We need a communication strategy to prepare development teams for this change, ensuring they understand the new tool and can leverage it to improve performance.

Objectives

Ensure smooth CPT adoption through clear documentation, proactive feedback collection, and transparent communication throughout the rollout.

Pre-rollout Tasks

Documentation & Preparation

  • Complete documentation
    • Test creation guidelines
    • Test stability expectations and current limitations
  • Merge the reporting MR
  • Validate new reporting functionality

Communication & Feedback

  • Create dedicated feedback issue for developer input
  • Prepare CPT job demonstration and reporting showcase

Rollout Communication Plan

Test Job Pre-merge Announcements with reporting disabled

  • Post initial announcement in #engineering-fyi and #development channels several days before merging MR !197705
    • Include link to feedback issue
    • Invite suggestions and concerns from development teams

Announcement for reporting enabled

  • Post announcement in #engineering-fyi and #development channels a day before merging the MR for enabling reporting
    • Include link to feedback issue
    • Invite suggestions and concerns from development teams
    • Include Action on devs

Post-merge Communication

  • Share rollout completion update in #engineering-fyi and #development
  • Include live demonstration of CPT functionality and reporting
Edited by Vishal Patel