Event Hubs Test Pipelines: Split out Management, Legacy Client, and Client Tests

[jsquire]

Summary

Currently, there is a single test pipeline for all libraries related to Event Hubs within the SDK, though the different categories are unrelated. When any library in the pipeline has test failures, the entire pipeline is reported as being in a failed state, which makes understanding the health of any single category difficult at a glance. In order to ensure that library authors are able to understand the health of their products with as little friction as possible, the pipeline should be broken down by category.

Scope of Work

• Break down the internal pipeline net - eventhub - tests into separate pipelines for:

  • The management clients
  • The legacy clients
  • The modern clients
    
    

• Coordinate with the Azure Developer Platform engineering team in order to ensure that the pipeline are configured correctly and follow the established patterns. (@weshaggard has offered to be the engineering point of contact and assist as needed)

Success Criteria

• The Event Hubs test pipeline has been split into multiple categories, as described in the scope.

• The ADP engineering team has reviewed the changes and approved.

• Each of the new pipelines can be run individually and test results mirror those from the nightly reports of the unified pipeline.

• The modern client live test suite continues to produce deterministic results and pass reliably.

References

• Example pipeline configuration (Storage)

[jsquire]

PRs are out but unlikely to be reviewed due to holiday staffing. Kicking forward to the next milestone to compensate.